All possible success and failure response status codes are documented with every endpoint in the API Reference.

Following is more detail on the format and purpose for each different HTTP response status code.

The HTTP status code will indicate the general category of the issue, while the response body will contain more details pertaining to the error.

 {  
     "status": 404,  
     "title": "Order Not Found Error",  
     "details": {  
         "description": "Order Not Found Error"
         "order_id": "6e225b1af09c469f94a1bb93ab7b533f"  
     }  
 }

HTTP Response Error Details

Status Type Explanation
400 request_validation_error Indicates that the request was malformed, un-parsable, or invalid in some way. Typically caused by improperly formatted or missing data. For example, an invalid date format, invalid ID format, data that exceeds the maximum length, or required data that is missing. The specific cause will be referenced in the extra content. Please refer to the API Reference for the expected format, maximum and minimum lengths, and required fields for every request.
401 unauthorized_error The authorization token was not recognized, or the token has expired.
404 menu_not_found_error The supplied Menu ID was not found.
404 order_not_found_error The supplied Order ID was not found. For example, an attempt to GET or DELETE an order ID that does not exist.
404 item_not_found_error Indicates that an Item ID supplied with a Create Order request does not exist.
406 delivery_not_available_error Returned in response to a Create Order request when delivery is not available to the supplied zip code or on the supplied delivery date. Be sure to check Availability prior to submitting a Create Order request.
406 item_not_available_error Returned in response to a Create Order request when an item is not available for delivery or sold-out to the supplied zip code on the supplied delivery date. Be sure to check Availability prior to submitting a Create Order request.
409 order_exists_error Indicates that the partner_ref_id included with a Order Create request already exists. partner_ref_id is used for idempotence prevention of duplicate requests, so must be unique for every Order.
409 incorrect_status_error Returned in response to a Cancel Order request that can not be processed due to the current Order status.
416 temperature_out_of_range_error Indicates that the forecast temperature for the requested delivery date / zip is above or below Intelligent Foods’s food-safe delivery thresholds. See Order and Shipment Status Codes for more details.
422 order_validation_error Indicates that some element of a Create Order request was incorrect. Unlike request_validation_error above, this error will not trigger on missing or malformed data, but more complex issues. Examples are the Menu is past deadline for ordering, the delivery date is not in the applicable week, a non-Protein item was ordered as a Protein, or the requested Protein is not available for the requested Meal.
422 address_validation_error Indicates that the street address supplied with a Create Order request was flagged as invalid. Intelligent Foods uses a 3rd party nation street address validation system.
500 internal_error An unexpected server error was encountered. Contact Intelligent Foods API support.
503 service_unavailable_error A temporary system error was encountered. If the problem persists, contact Intelligent Foods API support.