API terminology

A set of protocols, routines, and tools for building software applications that specify how software components should interact.

A request made by a client application to an API endpoint to retrieve data or perform an operation.

A software application or library that makes requests to an API.

A specific URL where an API can be accessed by a client application.

A server that acts as an API front-end, receives API requests, enforces throttling and security policies, and routes requests to backend services.

A unique identifier used to authenticate a user, developer, or calling program to an API.

A simple authentication method where a unique key is passed with each request.

A specific version of an API that may have different features, endpoints, or behaviors.

A unique identifier assigned to an application for API access and tracking purposes.

Specifies the media types that the client can handle in the response.

The MIME type for JSON data, commonly used in API requests and responses.

The MIME type for XML data.

The process of verifying the identity of a user or system making an API request.

The process of determining whether an authenticated user has permission to access specific resources or perform certain operations.

The root URL for an API that serves as the starting point for all API endpoints.

An access token that grants access to resources, typically passed in the Authorization header.

An authentication method where a token is passed in the Authorization header.

The status of a transaction indicating whether it has been finalized in the account (e.g., booked, pending).

A command-line tool for making HTTP requests, commonly used for testing APIs.

An authentication method using digital certificates for secure communication.

A digital certificate used by a client to authenticate itself to a server.

An HTTP header that indicates the media type of the request or response body.

A specific URL where an API can be accessed and a specific function can be performed.

A numeric or alphanumeric code that indicates a specific type of error in an API response.

A human-readable description of an error that occurred during an API request.

A rate limiting parameter that specifies how many times an API can be called per day.

Key-value pairs sent with HTTP requests and responses that provide additional information about the request or response.

The different types of requests that can be made to an HTTP server (GET, POST, PUT, DELETE, PATCH).

Three-digit codes returned by servers to indicate the result of an HTTP request (e.g., 200 OK, 404 Not Found).

The process of connecting different software systems or APIs to work together.

A lightweight data interchange format that is easy for humans to read and write.

The distribution of incoming API requests across multiple servers to ensure optimal resource utilization.

A simulated transaction used for testing purposes without affecting real data.

An API interaction pattern designed specifically for mobile applications.

An open standard for access delegation, commonly used for token-based authentication.

A more complex authentication framework that allows third-party applications to obtain limited access to user accounts.

A subscription key header used for authentication in Azure API Management services.

Variables in the URL path that are used to identify specific resources.

The data sent in the body of an HTTP request or response.

Key-value pairs added to the end of a URL to provide additional information to the server.

The practice of limiting the number of API requests a client can make within a specific time period.

The data sent in the body of an HTTP request, typically used with POST and PUT methods.

A unique identifier for an API request, used for tracking and debugging purposes.

The data returned by the server in response to an API request.

An architectural style for designing networked applications using standard HTTP methods.

An API that follows REST architectural principles.

A testing environment that allows developers to test API functionality without affecting production data.

A collection of software development tools and libraries for building applications that interact with an API.

A three-digit number returned by a server to indicate the result of an HTTP request.

A key that identifies a subscription to an API service, used for authentication and billing.

A separate environment used for testing API functionality before deploying to production.

The MIME type for plain text data.

The maximum amount of time to wait for an API response before considering the request failed.

A piece of data that represents authentication credentials or authorization permissions.

A testing phase where end users test the API to ensure it meets their requirements.

The address used to access a resource on the internet.

Identifies the client application making the request.

A 128-bit number used to uniquely identify information in computer systems.

The process of checking whether API input data meets the required format and constraints.

The management of changes to API versions and their corresponding documentation.

An API interaction pattern designed for web-based applications.

An HTTP header that contains a unique identifier for tracking requests across systems.