Skip to main content

Common API Errors (403, 429, 500) and How to Fix Them

Freddy Rodriguez avatar
Written by Freddy Rodriguez
Updated over 2 months ago

Sometimes, things don’t go as planned — and an API call returns an error. Below are a few of the most common error codes you might see when using Enrich Layer’s API, what they typically mean, and how to troubleshoot them quickly.

🔐 403 – Not Enough Credits

This error usually means you don’t have enough credits for the API call you’re trying to make.

Here’s what to check:

  • Make sure your credit balance is sufficient for the specific API request you’re sending.

  • Review your usage and ensure you’re not going over your available credits.

📩 Still seeing this? Reach out via the chat icon (bottom right) or email [email protected], and include the endpoint and request details — we’ll take a look and help you sort it out quickly.

🚦 429 – Rate Limit Exceeded

You’ve hit the maximum number of requests allowed in a short time frame.

How to fix:

  • Add a short delay (e.g., sleep or backoff logic) between requests.

  • If you’re running batch jobs or high-volume traffic, consider optimizing how frequently you’re calling the API.

  • Upgrading your plan may increase your rate limits.

📈 Tip: You can review your current rate limits in the API documentation or contact support for help optimizing usage.

🧱 500 – Server Error

This error is on our side. A 500 error means something went wrong on the server side.

What you can do:

  • Wait a moment and retry the request — this is often temporary.

  • If it continues, send us the request ID or error message you received so we can investigate.

When in Doubt, Reach Out

If you’re unsure what’s causing an error — or the fix doesn’t work — feel free to send us the details via chat or email. We’re happy to help debug it with you.


Did this answer your question?