Skip to main content
All V2 API error responses follow a standardized format:
Error responses never consume credits. The credits_consumed field will always be 0 on errors.

Error Codes Reference

Error Code Details

INVALID_API_KEY (403)

Returned when the x-api-key header is missing or contains an invalid key.
How to fix: Verify your API key in the dashboard and ensure it is included in the x-api-key header.

INVALID_ACCOUNT (404)

Returned when the account_id in the request body does not match any account under your API key.
How to fix: Call GET /v2/accounts to list your available accounts and use a valid account_id.

ACCOUNT_INACTIVE (403)

Returned when the account exists but is not currently active.
How to fix: Check the account status with GET /v2/accounts/{account_id}. To reactivate the account, log in again via POST /v2/login with the same credentials.

INVALID_ACTION (400)

Returned when the action field contains an unsupported action for the category endpoint.
How to fix: Refer to the documentation for the category you are calling to see available actions.

INVALID_PARAMS (400)

Returned when required parameters are missing or parameter values are invalid.
How to fix: Check the message field for the specific parameter issue and refer to the action’s documentation.

RATE_LIMITED (429)

Returned when you exceed the API rate limit.
How to fix: Implement exponential backoff in your requests. Wait a few seconds before retrying.

INSUFFICIENT_CREDITS (402)

Returned when your account does not have enough credits for the requested action.
How to fix: Top up your credits at app.linkupapi.com.

INTERNAL_ERROR (500)

Returned when an unexpected error occurs on the server.
How to fix: Retry after a few seconds. If the error persists, contact [email protected].