Error Reference

WhatsApp API Error Reference

Complete troubleshooting guide for WhatsApp API errors. 16 error codes across 8 categories.

16 error codes8 categoriesCloud API v21.0

Error Categories

Authentication

3 errors

Messaging Window

2 errors

Rate Limiting

1 error

Recipient

3 errors

Templates

3 errors

Media

2 errors

Content

1 error

Server

1 error

All Error Codes

#Authentication

10refresh-token

WhatsApp access has been revoked (OAuthException).

Solution:

Your WhatsApp Business account permissions were revoked. Reconnect your account through the Zernio dashboard to re-authorize access.

190refresh-token

WhatsApp access token is invalid or expired.

Solution:

The access token is no longer valid. This can happen after token expiration or a password change. Reconnect your WhatsApp Business account.

131031refresh-token

WhatsApp Business account has been locked.

Solution:

Your account was locked by Meta, usually due to policy violations. Check your account status in Meta Business Suite and appeal if necessary.

#Messaging Window

131051user-error

The 24-hour messaging window has expired.

Solution:

You can only send free-form messages within 24 hours of the customer's last message. After that, use an approved template message to re-initiate the conversation.

131026user-error

Customer has not messaged in over 24 hours. Re-engagement required.

Solution:

Send an approved template message to re-engage. Free-form messages are only allowed within the 24-hour customer service window.

#Rate Limiting

131047retry

WhatsApp rate limit reached.

Solution:

You've exceeded your phone number's messaging tier limit. Zernio handles this automatically with retries and exponential backoff. Your tier increases as your quality rating improves.

#Recipient

131021user-error

Invalid recipient phone number.

Solution:

The phone number is not valid or doesn't have WhatsApp. Ensure the number is in E.164 format (e.g., +14155552671) and the recipient has an active WhatsApp account.

131030user-error

Recipient phone number is not in the allowed list.

Solution:

In Meta's sandbox/test mode, you can only message pre-registered numbers. Add this number to your WhatsApp test recipients in the Meta Developer Dashboard, or switch to production mode.

receiver_incapableuser-error

Recipient does not have WhatsApp or cannot receive messages.

Solution:

The recipient's phone number is not registered on WhatsApp or their account cannot receive messages. Verify the number and try a different contact method.

#Templates

132000user-error

Message template not found.

Solution:

The template name or language code doesn't match any approved template. Double-check the exact template name and use the full language code (e.g., "en_US" not "en").

132001user-error

Message template is paused or disabled.

Solution:

Meta paused this template due to low quality or policy violations. Use a different template, or fix the issue and submit it for re-approval.

132007user-error

Invalid template parameters.

Solution:

The parameters you provided don't match the template's expected format. Ensure all required parameters are included and match the placeholder types (text, currency, date, etc.).

#Media

131052user-error

Could not download media from the provided URL.

Solution:

WhatsApp couldn't fetch the media file. Ensure the URL is publicly accessible, returns the correct Content-Type header, and the file is not behind authentication.

131053user-error

Unsupported media type or format.

Solution:

The media format is not supported. WhatsApp supports: images (JPEG, PNG), videos (MP4 with H.264), audio (AAC, MP3, OGG), and documents (PDF, DOC, XLS, etc.).

#Content

131048user-error

Message flagged as spam.

Solution:

WhatsApp's spam detection flagged your message. Review your content and messaging practices. Avoid sending identical messages to many recipients in quick succession.

#Server

500retry

WhatsApp service is temporarily unavailable.

Solution:

Meta's WhatsApp Cloud API is experiencing issues. Zernio automatically retries with exponential backoff. If the issue persists, check Meta's status page.

Best Practices

Error Handling

  • Implement automatic retries for rate limit and service errors
  • Store refresh tokens securely and handle token refresh flows
  • Log all errors with context for debugging
  • Show user-friendly error messages in your UI

Prevention Tips

  • Track the 24-hour messaging window per conversation
  • Validate phone numbers in E.164 format before sending
  • Pre-approve templates and test with all parameter variations
  • Use publicly accessible URLs for media attachments

Need Help with WhatsApp Integration?

Our API handles error scenarios automatically with smart retry logic and detailed logging.

SOC 2 CompliantGDPR Compliant