API Returning Errors
An API is how your website talks to another system — a payment provider, a CRM, or a delivery service, for example. When an API returns errors, that connection breaks and a feature stops working, even though the rest of the site looks fine.
API errors usually carry a code that tells us a great deal about the cause. This guide explains the common ones and what information helps us fix them.
Common Error Types
Most API errors fall into recognisable groups.
- 401 / 403: authentication or permission problems, often expired keys.
- 404: the requested resource was not found.
- 429: too many requests, a rate limit hit.
- 500: a fault on the other service's side.
What to Note
The right details speed up the diagnosis.
- Record the exact error code and message.
- Note which feature or integration is affected.
- Recall any recent change to keys or settings.
- Check whether the third-party service has reported an outage.
How We Resolve It
We can read the detailed logs, renew expired credentials, adjust request limits, and add graceful handling so a third-party hiccup does not break your page. Raise a ticket with the error code and the affected feature and we will reconnect it.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.