Development
Errors
Linkup API errors and how to handle them
This guide includes an overview of error codes you might see from both the API and our SDKs.
API Errors
Whatever the HTTP error code is, the response payload will contain the following object:
statusCode
: number - HTTP error code.
error
: object - Linkup error details containing:
code
: string - Error namemessage
: string - Description of the errordetails
: array - Details of the error. This array may be empty or include objects with the following properties:field
: string - The field that caused the errormessage
: string - A description of the field error
Here is an example:
API Error Codes
Code | Possible Reasons |
---|---|
400 - Bad Request | Required parameter is missing, or Invalid parameter or Search query yield no result |
401 - Unauthorized | API Key is missing or invalid |
403 - Forbidden | API key does not have permission to access this resource |
409 - Conflict | Resource conflict (e.g., duplicate entry or conflicting request) |
429 - Too Many Requests | You have run out of credit |
500 - Internal Server Error | Something’s up on our end |
SDK Errors
Python & JS SDK Error Types
Type | Reason |
---|---|
LinkupInvalidRequestError | Required parameter is missing, or invalid parameter |
LinkupNoResultError | Search query yield no result |
LinkupAuthenticationError | API Key is missing, invalid or you do not have permission to access this ressource |
LinkupInsufficientCreditError | You have run out of credit |
LinkupUnknownError | Anything else |