The Amplemarket API is a REST-based API that returns JSON-encoded responses and complies with the HTTP standard regarding response codes, authentication and verbs.

Production API access is provided via https://api.amplemarket.com base URL.

The media type used is application/vnd.amp+json

​

Authentication

You will be provided with an API Key that can then be used to authenticate against the Amplemarket API.

​

Authorization Header

The Amplemarket API uses API Keys to authenticate requests. You can view and manage your API keys from the Dashboard as explained in the getting started section.

All API requests must be made over HTTPS to keep your data secure. Calls made over plain HTTP will be redirected to HTTPS. API requests without authentication will also fail. Please do not share your secret API keys in publicly accessible locations such as Github repos, client-side code, etc.

To make an authenticated request, specify the bearer token within the Authorization HTTP header:

GET /email-validations/1
Authorization: Bearer {{api-key}}

curl /email-validations/1 \
  -H "Authorization: Bearer {{api-key}}

​

Limits

​

Rate Limits

The Amplemarket API uses rate limiting at the request level in order to maximize stability and ensure quality of service to all our API consumers.

By default, each consumer is allowed 500 requests per minute across all API endpoints, except the ones listed below. Users who send many requests in quick succession might see error responses that show up as status code 429 Too Many Requests.

If you need these limits increased, please contact support.

​

Endpoint specific limits

​

Usage Limits

Selected operations that run in the background also have limits associated with them, according to the following table:

​

Costs

Endpoints that incur credit consumption have the amount specified alongside selected endpoints in the API reference.

In the eventuality the account runs out of credits, the API will return an error with the error code insufficient_credits.