Zendesk API Errors 401, 422 and 429

How to fix it

Try these in order — the most common fix is first.

1. 1. Fix 401

   Copy steps
   1. Use email/token:API_TOKEN for Basic auth, or a Bearer token for OAuth
   2. Enable token access in Admin Center > Apps and integrations > APIs
   Did this fix it? Yes No

2. 2. Fix 422

   1. Read the details object in the response to find the invalid field
   Did this fix it? Yes No

3. 3. Fix 429

   Copy steps
   1. Read the Retry-After header and wait that long
   2. Batch requests and cache results to make fewer calls
   Did this fix it? Yes No

Symptoms

API calls return 401 Unauthorized, 422 Unprocessable Entity or 429 Too Many Requests.

Why it happens

• Wrong Basic auth format
• Invalid or missing field in the request body
• Too many requests per minute for your plan
• Token disabled in Admin Center

This guide also covers

• zendesk api 429
• zendesk api 401 unauthorized
• zendesk api 422

Other Zendesk errors

• Zendesk Emails Not Creating Tickets
• Zendesk Triggers Not Firing
• Zendesk Email Notifications Not Sending
• Zendesk Web Widget Not Loading or Not Showing
• Zendesk SSO Login Error (Redirected to Logout URL)
• Zendesk Macros Not Working or Not Showing
• Zendesk Attachment Too Large or Upload Refused
• Zendesk AI Agent Not Answering