Hypermedia

An index and topic collection covering hypermedia-driven APIs, HATEOAS, and the formats, link relations, and specifications that make APIs discoverable and self-describing. Hypermedia APIs use links, link relations, and embedded controls inside their responses so that clients can navigate an API graph at runtime rather than relying on hard-coded URI structures. This collection covers hypermedia formats including HAL, JSON:API, Siren, Collection+JSON, JSON-LD, Hydra, ALPS, UBER, Mason, and Verbose; the standards bodies that define web linking (IETF, W3C) including RFC 5988/8288 Web Linking and RFC 9264 api-catalog; provider APIs that demonstrably ship HATEOAS responses such as OpenProject, Reverb, MBTA, Patreon, Teamtailor, and Drupal JSON:API; and the spec libraries and frameworks (Spring HATEOAS, Spring Data REST, Apicurio) that implement hypermedia patterns.

Hypermedia is profiled on the APIs.io network. Tagged areas include Hypermedia, HATEOAS, HAL, JSON:API, and Link Headers.

The Hypermedia catalog on APIs.io includes 1 JSON-LD context.

Hypermedia’s developer surface includes developer portal and 1 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

9.6/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

0 APIs 6 Features 6 Use Cases

Hypermedia HATEOAS HAL JSON:APILink HeadersLink RelationsSirenCollection+JSONLinked Data JSON-LDHydraALPS

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 9.6/100 · minimal

Contract Quality 3.1 / 21

Developer Ergonomics 1.6 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.6 / 11

Contract Governance 0.0 / 10

Discoverability 4.1 / 9

Regulatory Posture 0.7 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hypermedia: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Features 6

Notable capabilities this provider offers.

HATEOAS Navigation

Hypermedia APIs include in-response links and link relations so clients can discover available state transitions at runtime rather than hard-coding URI templates against documen...

Standardized Hypermedia Formats

Established formats such as HAL, JSON:API, Siren, Collection+JSON, Hydra, ALPS, UBER, Mason, and Verbose provide structured ways to embed links, actions, and metadata inside API...

Web Linking via Link Headers

RFC 5988 and RFC 8288 define the HTTP Link header and the Web Linking model, including the IANA Link Relations registry that gives shared meaning to rel values across APIs.

Linked Data and Semantic Hypermedia

JSON-LD, Hydra, schema.org, and the broader RDF stack extend hypermedia with shared vocabularies, enabling semantic interoperability between APIs, search engines, and knowledge ...

Self-Describing API Catalogs

RFC 9264 api-catalog, APIs.json, and similar discovery documents act as hypermedia entry points that link a host to its APIs, OpenAPI specs, terms of service, and policies.

Hypermedia Frameworks and Libraries

Frameworks like Spring HATEOAS, Spring Data REST, and Apicurio provide implementation support for emitting HAL, HAL-FORMS, JSON:API, and Collection+JSON responses from server code.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Hypermedia Context

6 classes · 17 properties

JSON-LD

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

HALResource

2 properties

JSON SCHEMA

LinkRelation

11 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Hypermedia Hal Resource Structure

2 properties

JSON STRUCTURE

Hypermedia Link Relation Structure

11 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Hypermedia Hal Resource Example

5 fields

EXAMPLE

Hypermedia Link Relation Example

10 fields

EXAMPLE

Use Cases 6

What developers build with this provider.

Evolvable Long-Lived APIs

HATEOAS-based APIs allow servers to evolve URI structures, add new affordances, and deprecate endpoints over time while clients continue to navigate by link relations rather tha...

Domain-Driven Project Management APIs

OpenProject exposes work packages, projects, users, and attachments through a HAL+JSON hypermedia API where every resource embeds links to related resources and available actions.

Standardized CRUD via JSON:API

Patreon, MBTA, Teamtailor, and Drupal expose their resources via JSON:API, providing a consistent specification for fetching, including related resources, filtering, sorting, an...

Semantic Search and Structured Data

Schema.org and JSON-LD allow APIs and websites to publish machine-readable Linked Data that search engines, agents, and aggregators can consume without bespoke parsers.

API Discovery and Catalogs

APIs.json and RFC 9264 api-catalog documents act as hypermedia entry points that let crawlers, tooling, and AI agents discover an organization's APIs, specifications, and polici...

Hypermedia-Driven Web Apps

Approaches like htmx, hyperview, and Hypermedia Systems return HTML fragments and hypermedia controls directly to the client, simplifying applications by treating HTML itself as...

Integrations 8

Pre-built integrations with other platforms and tools.

HAL (Hypertext Application Language)

A minimal hypermedia format for JSON and XML that embeds _links and _embedded resources, widely used by APIs such as OpenProject, Reverb, and Spring Data REST.

JSON:API

A specification for building APIs in JSON that standardizes resource objects, relationships, includes, filtering, sorting, and pagination, used by Patreon, MBTA, Teamtailor, and...

Siren

A hypermedia specification for representing entities, their classes, properties, actions, and links, designed for rich, action-oriented hypermedia clients.

Collection+JSON

A JSON-based hypermedia format from Mike Amundsen for representing collections of items with queries and templates for write operations.

JSON-LD and Hydra

JSON-LD provides a JSON syntax for Linked Data; Hydra extends it with a vocabulary for describing hypermedia-driven Web APIs including operations, classes, and supported propert...

ALPS (Application-Level Profile Semantics)

A profile description format for documenting semantic descriptors and state transitions independent of any single media type.

Web Linking (RFC 5988 / RFC 8288)

IETF specifications defining the HTTP Link header and a model for typed web links, along with the IANA Link Relations registry shared across hypermedia formats.

Spring HATEOAS

A library for building hypermedia-driven REST APIs in Spring, supporting HAL, HAL-FORMS, Collection+JSON, and UBER, with first-class integration into Spring Data REST.

Scroll for all 8

Resources

Get Started 1

Portal, sign-up, and the first successful call

Portal

Portal

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Source (apis.yml)

aid: hypermedia
name: Hypermedia
description: An index and topic collection covering hypermedia-driven APIs, HATEOAS, and the formats, link relations, and
  specifications that make APIs discoverable and self-describing. Hypermedia APIs use links, link relations, and embedded
  controls inside their responses so that clients can navigate an API graph at runtime rather than relying on hard-coded URI
  structures. This collection covers hypermedia formats including HAL, JSON:API, Siren, Collection+JSON, JSON-LD, Hydra, ALPS,
  UBER, Mason, and Verbose; the standards bodies that define web linking (IETF, W3C) including RFC 5988/8288 Web Linking and
  RFC 9264 api-catalog; provider APIs that demonstrably ship HATEOAS responses such as OpenProject, Reverb, MBTA, Patreon,
  Teamtailor, and Drupal JSON:API; and the spec libraries and frameworks (Spring HATEOAS, Spring Data REST, Apicurio) that
  implement hypermedia patterns.
type: Index
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Hypermedia
- HATEOAS
- HAL
- JSON:API
- Link Headers
- Link Relations
- Siren
- Collection+JSON
- Linked Data
- JSON-LD
- Hydra
- ALPS
url: https://raw.githubusercontent.com/api-evangelist/hypermedia/refs/heads/main/apis.yml
created: '2026-05-19'
modified: '2026-05-19'
specificationVersion: '0.19'
apis: []
network:
- name: Apicurio
  url: https://raw.githubusercontent.com/api-evangelist/apicurio/refs/heads/main/apis.yml
- name: APIs.json
  url: https://raw.githubusercontent.com/api-evangelist/apis-json/refs/heads/main/apis.yml
- name: Design Patterns
  url: https://raw.githubusercontent.com/api-evangelist/design-patterns/refs/heads/main/apis.yml
- name: Drupal
  url: https://raw.githubusercontent.com/api-evangelist/drupal/refs/heads/main/apis.yml
- name: MBTA
  url: https://raw.githubusercontent.com/api-evangelist/mbta/refs/heads/main/apis.yml
- name: OpenProject
  url: https://raw.githubusercontent.com/api-evangelist/openproject/refs/heads/main/apis.yml
- name: Patreon
  url: https://raw.githubusercontent.com/api-evangelist/patreon/refs/heads/main/apis.yml
- name: RDF
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/apis.yml
- name: REST
  url: https://raw.githubusercontent.com/api-evangelist/rest/refs/heads/main/apis.yml
- name: RESTful
  url: https://raw.githubusercontent.com/api-evangelist/restful/refs/heads/main/apis.yml
- name: RESTful APIs
  url: https://raw.githubusercontent.com/api-evangelist/restful-apis/refs/heads/main/apis.yml
- name: RESTful Services
  url: https://raw.githubusercontent.com/api-evangelist/restful-services/refs/heads/main/apis.yml
- name: Reverb
  url: https://raw.githubusercontent.com/api-evangelist/reverb/refs/heads/main/apis.yml
- name: Schema.org
  url: https://raw.githubusercontent.com/api-evangelist/schema-org/refs/heads/main/apis.yml
- name: SPARQL
  url: https://raw.githubusercontent.com/api-evangelist/sparql/refs/heads/main/apis.yml
- name: Spring Boot
  url: https://raw.githubusercontent.com/api-evangelist/spring-boot/refs/heads/main/apis.yml
- name: Spring Boot 3
  url: https://raw.githubusercontent.com/api-evangelist/spring-boot-3/refs/heads/main/apis.yml
- name: Spring Data
  url: https://raw.githubusercontent.com/api-evangelist/spring-data/refs/heads/main/apis.yml
- name: Spring Framework
  url: https://raw.githubusercontent.com/api-evangelist/spring/refs/heads/main/apis.yml
- name: Teamtailor
  url: https://raw.githubusercontent.com/api-evangelist/teamtailor/refs/heads/main/apis.yml
- name: Technology Standards
  url: https://raw.githubusercontent.com/api-evangelist/technology-standards/refs/heads/main/apis.yml
- name: W3C
  url: https://raw.githubusercontent.com/api-evangelist/w3c/refs/heads/main/apis.yml
- name: Web Standards
  url: https://raw.githubusercontent.com/api-evangelist/web-standards/refs/heads/main/apis.yml
- name: Wikidata
  url: https://raw.githubusercontent.com/api-evangelist/wikidata/refs/heads/main/apis.yml
common:
- type: Portal
  url: https://apievangelist.com
- type: GitHubOrganization
  url: https://github.com/api-evangelist
- type: Features
  data:
  - name: HATEOAS Navigation
    description: Hypermedia APIs include in-response links and link relations so clients can discover available state transitions
      at runtime rather than hard-coding URI templates against documentation.
  - name: Standardized Hypermedia Formats
    description: Established formats such as HAL, JSON:API, Siren, Collection+JSON, Hydra, ALPS, UBER, Mason, and Verbose
      provide structured ways to embed links, actions, and metadata inside API responses.
  - name: Web Linking via Link Headers
    description: RFC 5988 and RFC 8288 define the HTTP Link header and the Web Linking model, including the IANA Link Relations
      registry that gives shared meaning to rel values across APIs.
  - name: Linked Data and Semantic Hypermedia
    description: JSON-LD, Hydra, schema.org, and the broader RDF stack extend hypermedia with shared vocabularies, enabling
      semantic interoperability between APIs, search engines, and knowledge graphs.
  - name: Self-Describing API Catalogs
    description: RFC 9264 api-catalog, APIs.json, and similar discovery documents act as hypermedia entry points that link
      a host to its APIs, OpenAPI specs, terms of service, and policies.
  - name: Hypermedia Frameworks and Libraries
    description: Frameworks like Spring HATEOAS, Spring Data REST, and Apicurio provide implementation support for emitting
      HAL, HAL-FORMS, JSON:API, and Collection+JSON responses from server code.
- type: UseCases
  data:
  - name: Evolvable Long-Lived APIs
    description: HATEOAS-based APIs allow servers to evolve URI structures, add new affordances, and deprecate endpoints over
      time while clients continue to navigate by link relations rather than hard-coded paths.
  - name: Domain-Driven Project Management APIs
    description: OpenProject exposes work packages, projects, users, and attachments through a HAL+JSON hypermedia API where
      every resource embeds links to related resources and available actions.
  - name: Standardized CRUD via JSON:API
    description: Patreon, MBTA, Teamtailor, and Drupal expose their resources via JSON:API, providing a consistent specification
      for fetching, including related resources, filtering, sorting, and pagination across very different domains.
  - name: Semantic Search and Structured Data
    description: Schema.org and JSON-LD allow APIs and websites to publish machine-readable Linked Data that search engines,
      agents, and aggregators can consume without bespoke parsers.
  - name: API Discovery and Catalogs
    description: APIs.json and RFC 9264 api-catalog documents act as hypermedia entry points that let crawlers, tooling, and
      AI agents discover an organization's APIs, specifications, and policies from a single well-known URL.
  - name: Hypermedia-Driven Web Apps
    description: Approaches like htmx, hyperview, and Hypermedia Systems return HTML fragments and hypermedia controls directly
      to the client, simplifying applications by treating HTML itself as the hypermedia format.
- type: Integrations
  data:
  - name: HAL (Hypertext Application Language)
    description: A minimal hypermedia format for JSON and XML that embeds _links and _embedded resources, widely used by APIs
      such as OpenProject, Reverb, and Spring Data REST.
  - name: JSON:API
    description: A specification for building APIs in JSON that standardizes resource objects, relationships, includes, filtering,
      sorting, and pagination, used by Patreon, MBTA, Teamtailor, and Drupal.
  - name: Siren
    description: A hypermedia specification for representing entities, their classes, properties, actions, and links, designed
      for rich, action-oriented hypermedia clients.
  - name: Collection+JSON
    description: A JSON-based hypermedia format from Mike Amundsen for representing collections of items with queries and
      templates for write operations.
  - name: JSON-LD and Hydra
    description: JSON-LD provides a JSON syntax for Linked Data; Hydra extends it with a vocabulary for describing hypermedia-driven
      Web APIs including operations, classes, and supported properties.
  - name: ALPS (Application-Level Profile Semantics)
    description: A profile description format for documenting semantic descriptors and state transitions independent of any
      single media type.
  - name: Web Linking (RFC 5988 / RFC 8288)
    description: IETF specifications defining the HTTP Link header and a model for typed web links, along with the IANA Link
      Relations registry shared across hypermedia formats.
  - name: Spring HATEOAS
    description: A library for building hypermedia-driven REST APIs in Spring, supporting HAL, HAL-FORMS, Collection+JSON,
      and UBER, with first-class integration into Spring Data REST.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
humanURL: https://apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/hypermedia"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/hypermedia/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hypermedia/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.