--- layout: default section: Guidance title: Technology of APIs summary: How we design, define, build, deploy, secure, and operate the connective tissue of the modern internet. nav: Guidance sub: Technology of APIs ---
{{ page.summary }}
The foundational version of HTTP that powers REST APIs.
Multiplexed connections and server push for faster API communication.
QUIC-based HTTP for low-latency API delivery.
Representational state transfer as the dominant HTTP API architectural style.
A query language and runtime for flexible API data fetching.
Google Remote Procedure Call as a high-performance binary API protocol.
The machine-readable contract standard for HTTP APIs.
The specification standard for event-driven and messaging APIs.
Vocabulary for annotating and validating JSON data structures.
A specification for building APIs in JSON with resource relationships.
Linked data format that brings semantic meaning to API payloads.
Linting rules for enforcing API design standards via Spectral.
High-performance OpenAPI linting rules via the Vacuum engine.
A versioning convention communicating the scope of API changes.
API design that embeds navigational links in responses.
HTTP callbacks that push events from producer to consumer.
Configurable targets for routing API events to downstream systems.
Architecture where APIs communicate through asynchronous event streams.
Architectural pattern of small independently deployable API services.
Function-as-a-service compute that powers on-demand API execution.
Human-readable reference material generated from API definitions.
Simulating API responses before the backend is built.
Verifying API behavior against the contract and expected outcomes.
Tools and libraries consumers use to call and interact with APIs.
Generated language-native libraries that wrap API operations.
Version control as the source of truth for API definitions and code.
Continuous integration and delivery pipelines for automating API lifecycle stages.
Integrated development environments with API tooling and governance inline.
AI coding assistants integrated into the API development workflow.
Protecting APIs from unauthorized access, abuse, and vulnerabilities.
Verifying the identity of API consumers before granting access.
API keys as the simplest token-based mechanism for authenticating requests.
The delegation framework for granting third-party API access.
Compact signed tokens for conveying API identity and claims.
Proxies that manage routing, authentication, rate-limiting, and observability for APIs.
Finding and cataloging APIs across an organization or the web.
Logs, metrics, and traces that reveal API runtime behavior.
Distributed tracing that follows a request across API service boundaries.
Model Context Protocol enabling AI agents to call tools and APIs.
Packaged capability units that AI agents load to execute API operations.