THE CORE AIM OF VOCABULARY MASTERY · API VOCABULARY · CLIENT → ENDPOINT → REQUEST → RESPONSE → CONTRACT
API vocabulary is the language used to describe how software systems communicate through defined interfaces. Terms such as endpoint, request, response, method, header, payload, status code, authentication, rate limit and webhook matter because an API is a contract between systems, not merely a URL.
The core aim of vocabulary mastery for API vocabulary is interface clarity. Learners should be able to explain who the client is, what resource or action an endpoint represents, what information is sent, what comes back, how access is controlled and what errors mean.
This page is the API Vocabulary owner inside the eduKateSG Vocabulary hub. For web usage, use Web Development Vocabulary. For software concepts, use Software Development Vocabulary.
Central proposition: API vocabulary is mastered when the learner can describe the interface contract from client request to server response, including data, authentication and failure conditions.
The 60-Second API Vocabulary Router
- Interface: API, endpoint, resource, route.
- Request: method, URL, header, query parameter, body.
- Response: status code, header, payload, error.
- Data: JSON, schema, field, serialization.
- Access: API key, token, authentication, authorization.
- Operations: rate limit, pagination, webhook, versioning.
The API Vocabulary Architecture
| Layer | Core terms | Core question |
|---|---|---|
| Client | consumer, SDK, request | Who is calling the API? |
| Endpoint | resource, route, method | What operation is being addressed? |
| Input | header, parameter, body | What information is sent? |
| Output | status code, payload, schema | What came back? |
| Security | authentication, authorization, token | Who may call it and what may they do? |
| Operations | rate limit, pagination, version | How is usage controlled over time? |
Endpoint and URL Are Not Always the Same Idea
A URL identifies a location. An endpoint is the callable interface represented by a location plus behaviour and contract. Two methods such as GET and POST may use the same path while representing different operations.
A Worked Example: GET vs POST
GET is commonly used to retrieve a representation of a resource. POST is commonly used to submit data for processing or create a subordinate resource, depending on API design. Method choice is part of the contract, not just syntax.
A Worked Example: Status Code
An HTTP status code communicates the broad result of a request. A 2xx code indicates successful handling, 4xx codes generally indicate client-side request problems, and 5xx codes generally indicate server-side failures. Exact meaning comes from the specific code and API contract.
Authentication and Authorization in APIs
Authentication verifies who the caller is. Authorization determines what the caller is allowed to do. APIs may use keys, tokens or other mechanisms, but the conceptual distinction remains the same.
API Vocabulary and JSON
Many web APIs exchange JSON. Useful terms include field, object, array, schema, serialization and validation. The vocabulary should connect to the exact data structure expected by the API.
Rate Limits, Pagination and Webhooks
Rate limiting controls how frequently a client may call an API. Pagination divides large result sets into manageable pages. A webhook reverses the usual polling pattern by letting one system send an event notification to another when something happens.
How to Learn API Vocabulary
- Use an API client or safe development environment.
- Read endpoint documentation.
- Inspect requests and responses.
- Compare methods and status codes.
- Practise authentication concepts without exposing real secrets.
- Use small JSON examples.
- Build one simple client–server integration.
Common API Vocabulary Mistakes
Calling every URL an API
Repair: identify whether the location exposes a defined software interface.
Confusing authentication and authorization
Repair: separate identity from permission.
Ignoring status codes
Repair: treat the response code as part of the contract.
Hard-coding secrets during practice
Repair: use safe secret-management patterns and test credentials where possible.
Frequently Asked Questions
What is API vocabulary?
It is the specialised language used to describe endpoints, requests, responses, data schemas, authentication, limits and events between software systems.
What API terms should beginners learn first?
Start with API, endpoint, request, response, method, header, body, JSON, status code and authentication.
What is an endpoint?
It is a defined callable interface where a client interacts with a service according to an API contract.
What is a webhook?
It is a mechanism where one service sends an event-driven HTTP request to another system when something occurs.
How can I learn API vocabulary?
Inspect real requests and responses in a safe environment and connect every term to the part of the exchange it describes.
Where This Article Fits in the eduKateSG Vocabulary Ecosystem
- Vocabulary Hub — the broad route.
- Web Development Vocabulary — browser and server integration.
- Software Development Vocabulary — application lifecycle.
- Networking Vocabulary — transport and protocols.
- Cybersecurity Vocabulary — API security.
The API Vocabulary Standard
API vocabulary reaches its core aim when the learner can look at documentation and explain the caller, endpoint, request, response, data format, permissions and failure conditions.
That is the standard: interface language clear enough for software systems to work together.