Skip to main content

Below you will find the most common status errors along with advice on how to fix the errors when using the HTTP/Batch API, Export API, Identify API, Attribution API, and Dashboard Rest API

 

HTTP/Batch API code errors:

 

200

Success

400

The expected JSON is formatted incorrectly. Check the HTTP/Batch API developers center article for formatting information.

413

The payload size is too big. The expected size is 1MB. Split the request into smaller batches and the try again.

429

Too many requests at a time for a given user. The limit is 10 events per second for each user. Stop sending events for 30 seconds before trying again.

500

A problem was encountered when processing your request. Try again and make sure you are including “insert_id” to avoid duplicate data.

 

Export API code errors:

 

200

Success

400

The file size of the exported data is too large. Shorten the time ranges and try again. The limit size is 4GB. 

404

Request data for a time range during which no data has been collected for the project, then you will receive a 404 response from our server.

504

The amount of data is large causing a timeout. For large amounts of data S3 destination is recommended.

 

Identify API code errors:

 

200

Success

414

A 414 error code, you might be using GET HTTP which has a limit on the URL. We recommend using HTTP POST instead of HTTP GET so the data is not in the URL.

429

Amplitude will throttle requests for device_ids or user_ids that exceed a certain threshold of events per second. When we throttle a request, the response will have HTTP status code 429.

 

Attribution API code errors:

 

200

Success

400

The expected JSON is formatted incorrectly. Check the Attribution API developers center article for formatting information.

 

Dashboard Rest API code errors:

 

200

Success

400

The expected JSON is formatted incorrectly. Check the Dashboard Rest API developers center article for formatting information. 

429

Limit request has been exceeded. The 429 response will  come with a message on how the limit is being exceeded.

 

Thanks Eddie!


Is there a reasoning for not returning 201 instead of 200 for the POST request? https://httpwg.org/specs/rfc7231.html#POST


Where are the not so common API error codes documented? I’m getting the following error using the Dashboard REST API

{
    "error": {
        "code": 229,
        "message": "Unable to create definition from arguments."
    }
}

 


Reply