Skip to content
>devspeak
← glossary
level 1Understanding Your Project

Response

also: responses, api response

The answer a server sends back after a request. It says whether things worked and includes any information that was asked for.

a bit more technical

The server's reply to a request, containing a status code (such as 200 for success or 404 for not found), headers, and often a body, commonly JSON data or an HTML page.

picture it

If a request is your order slip, the response is what comes back from the kitchen: your meal, or a note saying "sorry, we're out of salmon".

why it matters

Responses tell you what really happened. An agent that looks at the actual response, instead of guessing, can see whether the server refused, failed, or sent back the wrong data.

what your agent might say
agent
The response comes back with status 200 but an empty list, so the server isn't failing. It just isn't finding workouts for this user.
how you might use it
you → your agent
Show me the exact response the server returns when the coupon is rejected, including the status and any error message.
common mistake

Thinking a response always means success. Errors are responses too; the server is answering "no" or "something went wrong".

builds on