500 Internal Server Error

500 Internal Server Error

A 500 Internal Server Error indicates that an unexpected condition was encountered on the Chomp API servers, preventing it from fulfilling the request.

Common Causes

  • Backend Timeout: The database took too long to resolve a highly complex search query.
  • Malformed Input Handling: Your parameters were valid enough to bypass initial validation but caused an exception deeper in the system.
  • Infrastructure Issues: Temporary downtime or latency issues within the Chomp hosting environment.

Troubleshooting Steps

  1. Verify the current health of the API via the status page.
  2. Simplify your request parameters and try again.
  3. If you consistently receive 500 errors on specific queries, please open a support ticket so the engineering team can investigate the trace.


    • Related Articles

    • 400 Bad Request

      A 400 Bad Request error indicates that your API request is malformed or contains invalid parameters. Common Causes Type Mismatches: Passing a string value where the API strictly expects an integer or boolean. Malformed Syntax: Invalid formatting in ...

    • 404 Not Found

      A 404 Not Found error indicates that the Chomp API successfully processed your request, but the requested resource or food item does not exist in our database. Common Causes Missing Barcode: The UPC or EAN barcode you queried has not yet been indexed ...

    • 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 ...

    • Chomp API License Information

      This document outlines the Terms of Use ("Terms") governing your access to the Chomp API and the Chomp Database. By accessing the API, you consent to these Terms. Executive Summary & Operational Policies Commercial Use: Allowed on Standard and ...

    • 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 ...