By using the Lime Go API you can get notified when interesting things happen in your organization. You will for example get notified when a lead turns into a customer or when a deal is closed. When you get a notification the event will include information such as the deal's value or who closed the deal. You can also get notified when an organization's relation changes or when a deal's status changes.
The API supports both a push and pull model. If you want to use push you must set up a subscription by POST /event/subscription and provide a URL to which the API should send notifications.
If you use the pull model you should poll the FEED url at a regular interval.
We recommend that you use the push model.
When using the push model you should first create a subscription by POST to /event/subscribe. A subscription has a target URL and a set of events that it want to subscribe to.
When an event happens the Lime Go that is part of a subscription we will invoke the subscription's target URL.
A subscription is identified by an Id. If you want to unsubscribe invoke DELETE /event/subscription with the id as argument.
When using the pull model you must poll the Lime Go API at a regular interval for changes.
When something happens in the application, items are added to a queue of events. When you invoke GET feed you will get the events in chronological order (ie oldest first). You will get 50 items on each request. When an item has been retrieved it can't be retrieved again.
This means that the feed's position is managed by the server and the client can invoke the URL with the same query parameters each time.
You can't move the feed's position backwards or forwards.
You can set the responsible coworker for deals and organization. It is also possible to update an organization's relation or a deal's status. Read the /graphql endpoint for details about how to do this.
With the /graphql endpoint you can also search for data in Lime Go.
In order to use the API you must have an API key. You can generate an API key in Settings-Integrations-Lime Go API Keys.
The API key must be provided for all requests. It can be provided one of the the following ways:
|Header||The authorization header should be set according to :|
(note that there is no space between "go-api:" and the api key)
|Query parameter||Set a query parameted named apikey to your key:|
The API use json for all data. All request and response bodies should have Content-Type application/json.
You should set the Accept header to application/json or append .json on all requests.
A CORS policy is enabled which does not allow any cross origin requests to the API so the API should never be used in the client code of a website since the browser won't allow any requests to it.
The API is available at https://api.lime-go.com,
(Note that you will be unauthorized if you do not send the key as above)