The Imber REST API offers access and control over all Imber data (conversations, contacts and much more).
In order to access the Imber API, there are some things you first need to know.
Read the sections below before you start using the Imber API.
In order to use Imber API you must have a token for authentication, in order to get your unique TOKEN you can follow instructions below.
Go to Your Dashboard
Go to Setting
Go to Developers Section
Click on generate your Token
Copy your unique TOKEN and use it
Bearer authentication (also called token authentication) is an HTTP authentication scheme that involves security tokens called bearer tokens. The name “Bearer authentication” can be understood as “give access to the bearer of this token.” The client must send this token in the
Authorization header when making requests to protected resources:
Authorization: Bearer <token>
To ensure resiliency against DOS and enforce a fair-use policy, the Imber API has a rate-limit based on client IP and user identifier
Edge rate limit (a very permissive rate limit on Imber edge load balancers; you should not hit against this limit very often)
Global rate limit (a permissive, API-wide rate limit that limits the total amount of requests a given IP and user identifier can submit to the API)
If your client gets rate-limited, you will start receiving
429 Too Many Requests HTTP errors in response to your requests.
If you find any security hole in the Imber API, you are more than welcome to report it directly to
info [at] imber [dot] live