Error Handling

Not every API request will succeed—handling errors gracefully is essential for a stable integration. Weedmaps follows standard HTTP error codes to help you understand and address issues.

Common Error Scenarios

• 4xx Errors (Client-Side Issues):

  • 422 Unprocessable Entity: Common when creating or updating a menu item with invalid data, such as prohibited terms in name or description, or unsupported images.
  • 403/404/423 Errors: These typically indicate access issues or paused integrations—see Menu Access Guide for more.

• 5xx Errors (Server-Side Issues):

  • May occur during rare outages or platform instability.
  • Weedmaps treats 5xx errors as critical incidents—if you experience a sustained increase in 5xx errors, please contact us immediately.

Rate Limiting

Weedmaps enforces rate limits on all API traffic. If you encounter a 429 Too Many Requests, it means you have exceeded your allocation window.

For details on thresholds and mitigation strategies, see the Rate Limiting Guide.

Best Practices

• Implement retry logic with backoff for 5xx and 429 responses.
• Log 4xx errors for internal review—they indicate issues with your request data or authorization.
• Monitor and alert on 5xx error spikes and contact Weedmaps Support promptly if needed.