Zapier · API by Zapier
Domain not allowed
Short answer
This 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.
VerifiedLast verified
01Error text
Domain not allowed02Likely causes
- The domain in the step URL does not match the domain filter set when creating the connection.
- A typo in the step URL or the domain filter.
- A missing wildcard prefix, for example filtering for example.com when the endpoint uses api.example.com.
03How to fix it
- Open the Zap step and check the URL.
- Compare the step URL's domain with the domain filter in the connection. The domain must match one of the allowed domains.
- For subdomains, use a wildcard in the filter (for example
*.example.com) or include the specific subdomain. - If the filter must change, create a new connection with the correct domains.
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.
- 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