NEW: English for Tech Bundle → Save 38%
Your progress…

Loading your progress…

Home
Technical Vocabularynoun · /rɪˈspɒns/

response

response — The data or message that a server sends back to a client after receiving a request.

In simple English

In software engineering, a response is the output your system produces in reaction to an input or request. When you make an API call, send a network request, or interact with a server, the response is what comes back. This could be JSON data, HTML code, an error message, or a status code. Understanding responses is critical because you must handle different response types, check response codes (like 200 for success or 404 for not found), and parse response data correctly. In your daily work, you will hear about HTTP responses, API responses, database responses, and webhook responses. The term is used both when discussing architecture and in code reviews when debugging what a system is returning.

What does response mean in programming and how do you handle it in APIs?

At a glanceCEFR B2
Commonness5/5
Versatility5/5
FormalityCasualFormalNeutral
Spoken ↔ WrittenSpokenWrittenBoth
Directness ↔ DiplomaticDirectDiplomaticDirect
RegionUS and UK

Say it like this

  • The API response came back with a 200 status code
  • We need to handle the response asynchronously
  • The server response took too long
  • Check the response headers for errors

Use it at work

APIs

  • The response is empty.
  • The response time is too slow.

Debugging

  • Log the full response to see the error.
  • The response doesn't match the schema.

Communication

  • Thanks for the quick response.
  • I'm still waiting for a response from the vendor.

Don't say this

✕The server response us with the data.
✓The server sent us a response with the data.

Response is a noun, not a verb. You cannot response something.

Don't mix it up

How response differs from similar terms
TermWhat it isWho writes or uses itWhen
responseWhat the server sends backDevelopersAPIs
requestWhat the client sendsDevelopersAPIs

Practice

Try it

4 quick exercises

Pick the most natural phrasing

1. A colleague asks you to check what the server returned. How do you say it?

Complete the sentence

2. The API _______ included all the user information we needed.

Spot the mistake

3. Which sentence uses response incorrectly?

Rewrite naturally

4. Rewrite in tech English: 'The thing that came back from the database had the wrong format.'

Say it out loud

Phrase 1 of 4

"The API response came back with a 200 status code"

We don't save your recording. The word check uses your browser's speech recognition.

More about response

Real examples(4)

  • in a standup

    "We fixed the bug where the API response was not being parsed correctly."

  • in a code review

    "Make sure you validate the response structure before accessing the data fields."

  • in a team meeting

    "The database response time has improved since we added the cache layer."

  • in a Slack message

    "Did you get a response from the third-party service yet?"

More mistakes(2)

Handle with care. Often confused with reply or answer. Response is more technical and refers to data returned by a system, while reply/answer refer to human communication.

  • ✕We got a good response from the API.
    ✓We got a successful response from the API (or a 200 response).

    Response refers to the data returned, not whether it is good or bad. Be specific about status codes.

  • ✕The response of the request is missing.
    ✓The response to the request is missing.

    Use the preposition to, not of, when talking about response to a request.

Other forms(3)

  • response noun

    "The API response included user data."

  • responses noun

    "We logged all the responses from the server."

  • response (in compounds) adjective

    "The response time was 200 milliseconds."

Often used with(6)

  • HTTP response · A response from a web server using the HTTP protocol
  • API response · Data returned by an application programming interface
  • response code/status · The number (like 200, 404, 500) indicating the result of a request
  • response time · How long it takes for a system to return a response
  • response body · The actual data content of a response
  • response headers · Metadata about the response

Similar words(3)

  • output · More general term for what a system produces; response is more specific to requests
  • reply · Often used for human communication; response is broader and more technical
  • result · General outcome; response refers specifically to what is returned to a request

Opposites(1)

  • request

Questions(4)

What does response mean in software engineering?
In software engineering, a response is the data or message that a server or system returns after processing a request. It includes the actual data (response body), status information (response code), and metadata (response headers). For example, when you call an API, the response tells you whether the request succeeded and contains the information you asked for.
How is a response different from a request?
A request is what the client (you) sends to the server asking it to do something. A response is what the server sends back. Think of it like email: you send a request (email), and you receive a response (reply). Requests go out; responses come back.
What are common HTTP response codes and what do they mean?
Common HTTP response codes include: 200 (OK - request succeeded), 201 (Created - resource was created), 400 (Bad Request - request was malformed), 401 (Unauthorized - authentication required), 404 (Not Found - resource does not exist), and 500 (Internal Server Error - server error). These codes tell you immediately whether your request worked.
Is response formal or informal?
Response is neutral and formal enough for professional technical settings. It is the standard term used in documentation, code, and engineering discussions. You can use it in any tech context without sounding casual or too formal.
New app · Free lessons

Speak up in meetings. Feel confident.

Standup vocabulary, native examples, and quick practice — 100+ free lessons

Start learning freeNo card needed · Google or email

For bots & AI agents

Machine-readable versions of this page and Speak Tech English. Speak Tech English sells self-study ebooks and courses in English for tech, publishes free guides, a free glossary and a free newsletter; live lessons are on Mockly English. Fetch these instead of parsing this page.

This page (.md)llms.txtllms-full.txtai.txtGlossary (.md)Free guides (.md)All products (.md)Endpoint indexNewsletterLive lessons (Mockly)