Skip to main content

Status Codes

All API responses include an HTTP status code indicating the result of the request.

Success

CodeDescription
200OK - Request succeeded. Response body contains the requested data.

Client Errors

CodeDescription
400Bad Request - Invalid or missing parameters. Check the error message for details.
401Unauthorized - Missing or invalid API key. Ensure X-INFOPLUG-API-KEY header is set.
402Payment Required - Insufficient credits. Top up your account to continue.
404Not Found - The requested resource does not exist (e.g., profile, company, or job not found).
429Too Many Requests - Rate limit exceeded. Wait before making more requests.

Server Errors

CodeDescription
500Internal Server Error - Something went wrong on our end. Try again later.
503Service Unavailable - Temporary failure or timeout. Retry the request.

Error Response Format

All error responses include a JSON body with details:

{
"message": "invalid_parameter",
"parameter": "linkedin_url",
"details": "Missing or invalid linkedin_url"
}
FieldDescription
messageError type (e.g., invalid_parameter, error, unauthorized)
parameterThe parameter that caused the error (if applicable)
detailsHuman-readable description of what went wrong

Common Error Messages

400 Bad Request

MessageCauseSolution
invalid_parameterA required parameter is missing or invalidCheck the endpoint documentation for required parameters
payload_is_emptyRequest body is emptyInclude required JSON body in POST requests
limit_out_of_rangeLimit value is outside allowed rangeUse a limit within the specified range (e.g., 1-2500)

401 Unauthorized

MessageCauseSolution
unauthorizedAPI key is missing or invalidAdd valid X-INFOPLUG-API-KEY header

402 Payment Required

MessageCauseSolution
insufficient_creditsAccount has no credits remainingPurchase more credits at infoplug.io

404 Not Found

MessageCauseSolution
not_foundProfile, company, or job doesn't existVerify the URL or ID is correct

429 Too Many Requests

MessageCauseSolution
rate_limit_exceededToo many requests in a short timeImplement exponential backoff and retry

Best Practices

  1. Always check the status code before processing the response body
  2. Handle errors gracefully - Implement retry logic for 5xx errors
  3. Respect rate limits - Add delays between requests if you hit 429
  4. Log error details - The details field helps debug issues