Atom Publishing Protocol (RFC 5023)
RFC 5023 (2007), the editing half of Atom — collections you POST entries into, service documents that describe them, ETag-conditioned updates, and media resources whose binary content is posted separately from the entry that describes it. It is the standards-track origin of the “metadata and bytes are different resources” pattern that every modern upload API uses, and it was the HTTP API that Google, Microsoft and the blogging platforms built on in the late 2000s.
Also known as AtomPub, APP, RFC 5023.
Providers that carry Atom Publishing Protocol 3
These providers' own APIs.json profiles carry Atom Publishing Protocol as a tag — the provider's statement that the standard is part of what it does. APIs.io has not verified the implementation on this page; the de facto profiles on this site are where that measurement exists. Ordered by Kin Score.
Read from the API Evangelist standards directory, facts verified 2026-10-07. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.