Web API Standards Reference
Modern web API standards: Fetch API, WebSockets, WebRTC, Web Workers, Service Workers, and WebAssembly with specs and use cases.
Web platform API standards with the specification that defines each and a short description: Fetch, WebSockets, WebRTC, Web Workers, Service Workers and WebAssembly, extended with WebAuthn, WebTransport, Server-Sent Events, Streams, IndexedDB, Web Components, WebGPU and the Push API.
Use it when
- You need to know which standard defines a web capability and who maintains it.
- You are comparing real-time communication options.
Watch out for
- Specifications and implementations evolve independently; a standard may be only partly implemented.
- Maintainers differ: WHATWG, W3C and the IETF each own different parts of the platform.
The data
Standards
14 rows
| Name | Spec | Description |
|---|---|---|
| Fetch API | WHATWG | Modern interface for network requests, replacing XMLHttpRequest |
| WebSockets | RFC 6455 | Full-duplex communication over single TCP connection |
| WebRTC | W3C / IETF | Real-time peer-to-peer audio, video, and data communication |
| Web Workers | WHATWG | Background JavaScript execution in separate threads |
| Service Workers | W3C | Proxy scripts for caching, push notifications, offline support |
| WebAssembly | W3C | Binary instruction format for stack-based virtual machine |
| WebAuthn | W3C | Public-key credential API for passkeys and phishing-resistant authentication |
| WebTransport | W3C and IETF | Low-latency bidirectional streams and datagrams over HTTP/3 |
| Server-Sent Events | WHATWG HTML | One-way server-to-client event stream over HTTP |
| Streams API | WHATWG | Process data incrementally as readable, writable and transform streams |
| IndexedDB | W3C | Transactional client-side database for structured data and blobs |
| Web Components | WHATWG and W3C | Custom elements, shadow DOM and templates for reusable encapsulated components |
| WebGPU | W3C | Modern API for GPU graphics and general-purpose computation in the browser |
| Push API | W3C | Lets a service worker receive messages from a server even when the page is closed |
Fields
The shape of this dataset, read from the data itself: every column, its type and a real value. Agents can use this to plan a query without fetching the whole document.
| Section | Field | Type | Example |
|---|---|---|---|
| standards | name | string | Fetch API |
| standards | spec | string | WHATWG |
| standards | description | string | Modern interface for network requests, replacin… |
Fetch the same bytes
The static files contain the same reference rows as the API, with no API rate limit. Live metadata, such as view counts, may differ. Use the API for content negotiation; use the static files for a cacheable snapshot.
curl "https://yjtoon.yunusemrevurgun.com/api/dataset/web-api-standards?format=toon"
const res = await fetch( "https://yjtoon.yunusemrevurgun.com/static-data/dataset/web-api-standards.toon" ); const toon = await res.text();
Rate limit: 120 requests per minute per IP, no key and no signup. API reference →