RFC 9727: api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
In plain English — editorial summary, not part of the RFC
This document defines the "api-catalog" well-known URI and link relation. It is intended to facilitate automated discovery and usage of published Application Programming Interfaces (APIs). A request to the api-catalog resource will return a document providing information about, and links to, the Publisher's APIs.
Document record
- Document ID
- RFC9727
- Published
- June 2025
- Authors
- K. Smith
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9457Problem Details for HTTP APIsCurrent
July 2023
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 9290Concise Problem Details for Constrained Application Protocol (CoAP) APIsCurrent
October 2022
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 8952Captive Portal ArchitectureCurrent
November 2020
- RFC 8631Link Relation Types for Web ServicesCurrent
July 2019
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?