Jotting one man's journey through software development, programming, and technology
◀️ Home
Example:
https://asset-check.run.app/results?ids=20251015120903_RECKITT_Nurofen_LasVegas_020_004_AT,20251015120903_FY23Q4_Pepsi_MOVIES_Sleek_Black_Fantasy_16x9_6s_1
https://asset-check.run.app/results?ids=20251015120903_RECKITT_Nurofen_LasVegas_020_004_AT,20251015120903_FY23Q4_Pepsi_MOVIES_Sleek_Black_Fantasy_16x9_6s_1Whenever we visit some type of website we refer to it as the client, or the frontend. Behind the scenes, that frontend is communicating with some type of API (Application Programming Interface) - which is running on a different server - through requests and responses.
We can think of an API as a backend server that handles all data operations (e.g. creating, reading, updating, deleting).
The request is what we send from the frontend to the backend essentially saying what we want to do. The response is what comes back from the backend to our the client.
The path identifies the resource or action in the API.
Example: /users/42/orders means “orders that belong to user 42”.
The request body contains the data you send to the server (usually JSON).
Common with POST, PUT, and PATCH.
Example:
{ "name": "Alice", "role": "admin" }
Headers provide extra metadata about the request. Common headers:
Authorization: who is making the requestContent-Type: format of the body (for example application/json)Accept: response format expected by the clientThe status code tells you if the request succeeded or failed.
2xx: success4xx: client-side issue (bad request, unauthorized, not found)5xx: server-side issue
The response body is the actual data returned by the server. It can contain results, created/updated data, or an error message.
Response headers provide metadata about the response. Examples:
Content-Type: response formatCache-Control: caching behaviorSet-Cookie: sends/updates cookies in the browser