> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/api/api-basics/terminology.md). # Terminology
TermExplanation
API (Application Programming Interface)A set of rules that allows two software systems to communicate. It defines how requests should be made and what responses to expect.
ClientThe system (like a browser or mobile app) that sends requests to an API.
ServerThe system that receives API requests, processes them, and returns responses.
EndpointA specific URL or route in an API that represents an action or data source. Example: /users or /products/123.
RequestThe message sent by the client to the API, asking for data or action.
ResponseThe message sent by the API back to the client after processing a request.
HTTP Method (Verb)The action the client wants to perform. Common ones: GET (read), POST (create), PUT (update), DELETE (remove).
ResourceA unit of data in an API. In REST APIs, resources are typically represented as nouns in the URL, such as users, orders, or products.
Path ParameterA variable in the URL path used to identify a specific resource. Example: /users/{id}.
Query ParameterA key-value pair added to the URL to filter or refine the request. Example: /users?active=true.
HeaderKey-value pairs sent along with the request or response to provide metadata like content type or authorization.
BodyThe main content or data sent with a request (especially in POST, PUT) or returned in a response.
Status CodeA numeric code in the response that tells whether the request succeeded or failed. Example: 200 OK, 404 Not Found.
AuthenticationThe process of verifying the identity of the client making the API call.
API ConsumerThe system or developer that uses the API to perform operations or access data.
API ProviderThe system or service that exposes the API and responds to incoming requests.
StatelessnessA principle where each API request is independent and doesn't rely on past requests. Common in REST APIs.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.pranaypourkar.co.in/the-programmers-guide/api/api-basics/terminology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.