Zapier · API by Zapier
401 or 403 errors in API by Zapier
Short answer
A 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.
VerifiedLast verified
01Error text
401 (Unauthorized)
403 (Forbidden)02Likely causes
- The API key or OAuth2 token has expired or been revoked.
- OAuth2 scopes do not include the permissions the endpoint requires.
- The API key does not have access to the requested resource.
- For Query Parameter (API key) authentication, the parameter name does not match what the API expects.
03How to fix it
- Go to the Apps page and find the API by Zapier connection. If it shows an error, create a new connection with updated credentials.
- Verify with the API provider that the credentials have the required permissions.
- For OAuth2, confirm the connection's scopes match what the endpoint requires, and create a new connection with updated scopes if needed.
04Official documentation
→Related errors
- 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.
- 4xx or 5xx errors from the API in API by ZapierThese 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.
- 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