/LinkdAPI Error Handling and Troubleshooting
Troubleshooting

LinkdAPI Error Handling and Troubleshooting

Published August 1, 2025
Updated July 31, 2025
1 min read
LinkdAPI Error Handling and Troubleshooting

LinkdAPI returns consistent and informative error messages. Always check for success: false and review the statusCode and message.

Too Many Requests (Example Developer tier, the message will vary based on your current tier)

{
  "success": false,
  "statusCode": 429,
  "message": "Too many requests for your tier \"Developer\". You've reached the highest tier.",
  "errors": {
    "current_limit": "25 requests/minute",
    "current_tier": "Developer"
  },
  "data": null
}

Missing API Key

{
  "success": false,
  "statusCode": 401,
  "message": "Missing API Key in X-linkdapi-apikey header",
  "errors": null,
  "data": null
}

Route Not Found

{
  "success": false,
  "statusCode": 404,
  "message": "Route not found",
  "errors": null,
  "data": null
}

⚡ Pro Tip:
Set up a cron job to regularly check the health of the API by sending a request to https://linkdapi.com/status


If you receive an unexpected error, double-check your endpoint, method, or API key. Still stuck? Reach out to [email protected].

Was this article helpful?

Your feedback helps us improve our documentation

Still need help? Our support team is here for you.