Fundamentals
Data
Data onboarding
Lexer data specification
Getting started with APIs
Lexers APIs
Customer data
Datasets
Logs
Forms
Lexer Javascript Tag
Data off-boarding
Understand
Engage
Activate
Respond
Schedule
Measure
Track
Activity
Listen
Visualize
Report
Response codes and common errors
When Lexer receives a request to an API endpoint a number of different HTTP status codes may be returned in response, depending on the original request.
Lexer tip
We recommend relying on the response code versus the response body in your implementation.|
200 OK |
The request was successfully processed. |
|
201 Created |
The request has been fulfilled and a new resource has been created. |
|
202 Accepted |
The request has been accepted but not yet processed. |
|
400 Bad Request |
The request wasn't understood by the server, generally due to incorrect parameters. |
|
401 Unauthorized |
The necessary API tokens are not present in the request or are incorrect. |
|
404 Not Found |
The requested resource was not found. |
|
429 Too Many Requests |
The request was not accepted because the application has exceeded the rate limit. |
|
500 Internal Server Error |
An internal error occurred. Please check our status page (https://status.lexer.io) or contact support@lexer.io if you have ongoing issues. |
|
503 Service Unavailable |
The server is currently unavailable. Please check our status page (https://status.lexer.io) or contact support@lexer.io if you have ongoing issues. |
