An API response is the reply a service sends after a request. You do not need to understand the whole application to read the useful parts. Begin with the status code, then look at the response body and any request identifier.
200 range: the request normally succeeded
Before you start
Codes in the 200 range usually mean the request worked. A 400-range code usually points to the request, identity, permission, or missing item. A 500-range code usually means the service failed while handling a valid-looking request. The body often adds a plain message and an error code.
Did the request succeed?
What data or explanation came back?
How can support find this exact attempt?
Follow these steps
Start with the three-digit HTTP code.
Find data, message, error, and identifier fields.
Hide tokens, keys, personal data, and full headers.
Save time, endpoint, status, message, and request ID.
In JSON, braces contain an object, square brackets contain a list, and each named field has a value. Search for fields such as id, status, message, error, created_at, or next_page. Do not paste an API key, access token, or full customer response into a public forum.
Check your result
- No API key or bearer token is in the screenshot.
- The endpoint and time are recorded.
- The status code and error text are copied exactly.
- A retry will not create a duplicate payment or record.
Save the time, endpoint, status code, safe part of the body, and request ID. That is enough for a developer or support team to find the failing request without receiving the secret used to send it.