Browser Requests and CORS Support
The Chomp API fully supports Cross-Origin Resource Sharing (CORS) and standard client-side browser requests, including AJAX and fetch API implementations.
For specific implementation details and examples, please refer to the API Documentation.
Related Articles
Rate Limits & Requests Per Minute (RPM)
A rate limit defines the maximum number of API calls your application can make within a one-minute window. Rate limits are enforced to maintain platform stability and ensure equitable resources for all developers. If your application exceeds its ...
Contacting Support
If an integration issue or billing question cannot be resolved using the Knowledge Base or API Documentation, direct assistance is available. Please open a support ticket and provide detailed information regarding the issue, including the associated ...
401 Unauthorized
A 401 Unauthorized error indicates that the Chomp API has rejected your request due to authentication, billing, or rate limit issues. Common Causes Exceeded Rate Limits: (Limited and Standard Plans) You have exceeded your allowed Requests Per Minute ...
Monitoring API Usage
API usage, including request volume and billing estimates, must be monitored via the Client Center. The Client Center provides a detailed breakdown of all active subscriptions associated with an account. Available metrics include: Total API requests ...
Troubleshooting Barcode Matches
The Chomp database contains millions of branded food products indexed primarily by GTIN-12 (UPC-A) and GTIN-13 (EAN-13) barcode formats. If you are calling the /food/branded/barcode.php endpoint and receiving empty results or a 404, the issue is ...