Zapier · API by Zapier
4xx or 5xx errors from the API in API by Zapier
Short answer
These status codes in an API by Zapier step come from the API being called, not from Zapier. Check the endpoint URL and request against the provider documentation, add a delay for rate limits, and retry later for 5xx errors.
VerifiedLast verified
01Error text
400
404
429
500
502
50302Likely causes
- 400 Bad Request: the request body or parameters are formatted incorrectly.
- 404 Not Found: the endpoint URL is wrong or the resource does not exist.
- 429 Too Many Requests: the API provider's rate limit was exceeded.
- 500, 502 or 503: the API provider's server has issues.
03How to fix it
- Check the endpoint URL for typos.
- Review the request body and parameters against the API provider's documentation.
- If you exceed rate limits, reduce the Zap's frequency or add a Delay step before the API by Zapier step.
- For 5xx errors, wait and try again. If they persist, check the API provider's status page.
04Official documentation
→Related errors
- 401 or 403 errors in API by ZapierA 401 or 403 from an API by Zapier step means the credentials expired, were revoked, or lack the permissions or scopes the endpoint requires. Create a new connection with updated credentials and confirm the permissions with the API provider.
- Domain not allowedThis API by Zapier error means the domain in the step URL does not match the domain filter set when the connection was created. Compare the two, use a wildcard for subdomains, or create a new connection with the correct domains.
- JSON errors in the request bodyA JSON parsing error in an API by Zapier step means the request body is not valid JSON. Validate the body, quote mapped fields properly, and escape special characters with a Formatter step.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Zapier work:Open Zapier jobsZapier rates and salaries