REST

REST Architectural Style

Representational State Transfer (REST) is an architectural style originally defined by Roy Fielding. REST provides six guiding constraints: client-server separation, statelessness, cacheability, uniform interface, layered system, and optional code-on-demand. Any API conforming to these constraints is considered RESTful.

GitHub

Documentation

📖
Documentation
https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

Other Resources

🔗
Specification
https://www.rfc-editor.org/rfc/rfc7231
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/rest/refs/heads/main/apis.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/rest-architectural-style"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: rest:rest-architectural-style
name: REST Architectural Style
description: 'Representational State Transfer (REST) is an architectural style originally defined by Roy
  Fielding. REST provides six guiding constraints: client-server separation, statelessness, cacheability,
  uniform interface, layered system, and optional code-on-demand. Any API conforming to these constraints
  is considered RESTful.'
humanURL: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
tags:
- Architecture
- HTTP
- REST
- Web Services
properties:
- type: Documentation
  url: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
- type: Specification
  url: https://www.rfc-editor.org/rfc/rfc7231