Skip to main content
All V2 API error responses follow a standardized format: 
{
  "success": false,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable description of the error"
  },
  "metadata": {
    "action": "the_action_attempted",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
Error responses never consume credits. The credits_consumed field will always be 0 on errors.

​
Error Codes Reference

Error CodeHTTP StatusDescription
INVALID_API_KEY403 ForbiddenThe provided API key is invalid, expired, or missing from the x-api-key header.
INVALID_ACCOUNT404 Not FoundThe specified account_id does not exist or does not belong to your API key.
ACCOUNT_INACTIVE403 ForbiddenThe account exists but is currently inactive or suspended. Reactivate the account before making requests.
INVALID_ACTION400 Bad RequestThe requested action is not supported for this category endpoint. Check the available actions in the documentation.
INVALID_PARAMS400 Bad RequestOne or more required parameters are missing, or a parameter value is invalid. Check the message field for details.
RATE_LIMITED429 Too Many RequestsYou are sending too many requests. Slow down and retry after a short delay.
INSUFFICIENT_CREDITS402 Payment RequiredYour account does not have enough credits to perform this action. Top up your credits to continue.
INTERNAL_ERROR500 Internal Server ErrorAn unexpected server error occurred. If this persists, contact support.

​
Error Code Details

​
INVALID_API_KEY (403)

Returned when the x-api-key header is missing or contains an invalid key. 
{
  "success": false,
  "error": {
    "code": "INVALID_API_KEY",
    "message": "The provided API key is invalid or missing"
  },
  "metadata": {
    "action": "get_profile",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
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. 
{
  "success": false,
  "error": {
    "code": "INVALID_ACCOUNT",
    "message": "The specified account_id does not exist"
  },
  "metadata": {
    "action": "get_profile",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
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. 
{
  "success": false,
  "error": {
    "code": "ACCOUNT_INACTIVE",
    "message": "This account is currently inactive"
  },
  "metadata": {
    "action": "get_profile",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
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. 
{
  "success": false,
  "error": {
    "code": "INVALID_ACTION",
    "message": "Unknown action 'foo_bar' for category 'profiles'"
  },
  "metadata": {
    "action": "foo_bar",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
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. 
{
  "success": false,
  "error": {
    "code": "INVALID_PARAMS",
    "message": "Missing required parameter: profile_url"
  },
  "metadata": {
    "action": "get_profile",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
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. 
{
  "success": false,
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. Please try again later"
  },
  "metadata": {
    "action": "get_profile",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
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. 
{
  "success": false,
  "error": {
    "code": "INSUFFICIENT_CREDITS",
    "message": "Insufficient credits. This action requires 3 credits, but you have 1 remaining"
  },
  "metadata": {
    "action": "search_profiles",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
How to fix: Top up your credits at app.linkupapi.com.

​
INTERNAL_ERROR (500)

Returned when an unexpected error occurs on the server. 
{
  "success": false,
  "error": {
    "code": "INTERNAL_ERROR",
    "message": "An unexpected error occurred while processing your request"
  },
  "metadata": {
    "action": "get_profile",
    "credits_consumed": 0,
    "timestamp": "2026-03-24T12:00:00Z"
  }
}
How to fix: Retry after a few seconds. If the error persists, contact [email protected].