Introduction
To implement the API, you need the following:
Active Smart Sender account and created project.
Account authentication token (API token / Access token) - a unique account identifier used to verify your account in all API requests.
Important note for developers: The Smart Sender API has a limit of 180 requests per minute.
When this limit is exceeded, a 60 second lock occurs for the first time. Each time the line limit is exceeded, the blocking increases by 60 seconds (the second exceeding - a blocking of 120 seconds, the third - 180, etc.), but no more than 720 seconds of blocking.
You can control the number of requests allowed with the X-Rate-Limit header.
Authentication token
An authentication token (also known as an application key) is a unique and secret identifier for an account. It is used to authenticate the request to the Smart Sender API and to prevent third parties from sending requests on behalf of the project. Each API request must contain an HTTP header named Authorization containing the account's authentication token.
HTTP header
| Code Block |
|---|
Authorization: Bearer O1CpCRhOVuXpMVf5e0An9DMwrn8w7b8CwskbhIBUjgOJ3B2vYzbFZum3oBOF |
An authentication token is generated when a project is created and can be viewed or modified by project administrators on the Integrations tab of the selected project.
Note. If you don't send the auth token in the header, it will result in an error with the message "Unauthenticated".