An HTTP status code describes a request’s protocol-level outcome. MDN groups codes into informational responses, success, redirects, client errors and server errors. Common examples include 200 for an OK response and 404 when the requested resource cannot be found. Source: MDN: HTTP response status codes

Read the application response as well

For a booking integration, ask the technical team what the response body says about the actual reservation. Do not use the status number alone as the customer-facing booking status. The request and the business action need to be interpreted together using the provider’s documentation.

Give support the surrounding evidence

Record the operation, time, status code and request identifier where available. Include a redacted response through the approved support route. This gives the investigation more context than a screenshot containing only “an error occurred”.

If a write request ends ambiguously, follow the provider’s documented recovery process before repeating it. Stripe’s error guidance illustrates that a network failure can leave the outcome unknown, so lack of a response is not proof that nothing happened. Source: Stripe: advanced error handling

Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.