Formality API

The Formality REST API exposes the workspace contract repository so external tools and AI agents can retrieve documents and the AI-extracted metadata layer. Every path is namespaced to a workspace — /api/v1/{workspaceId}/ — and the documented resources cover agreements and agreement fields, with the help centre describing coverage of agreements, counterparties and related entities. Access uses a two-step bearer flow: an administrator mints a long-lived personal Refresh Token in Personal Settings > Formality API, then exchanges it at GET /api/v1/token for a 5-minute access token used as Authorization: Bearer on subsequent calls. A Swagger UI is published at /-/api-doc-swagger but is reachable only after authenticating.

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/formality-api"
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 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.

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

API entry from apis.yml

apis.yml Raw ↑
aid: formality-api
name: Formality API
description: 'The Formality REST API exposes the workspace contract repository so external tools and AI
  agents can retrieve documents and the AI-extracted metadata layer. Every path is namespaced to a workspace
  — /api/v1/{workspaceId}/ — and the documented resources cover agreements and agreement fields, with
  the help centre describing coverage of agreements, counterparties and related entities. Access uses
  a two-step bearer flow: an administrator mints a long-lived personal Refresh Token in Personal Settings
  > Formality API, then exchanges it at GET /api/v1/token for a 5-minute access token used as Authorization:
  Bearer on subsequent calls. A Swagger UI is published at /-/api-doc-swagger but is reachable only after
  authenticating.'
humanURL: https://help.formality.com/integrations/api
baseURL: https://app.eu1.formality.com/api/v1/{workspaceId}
tags:
- Contract Management
- Documents
- Legal
- Agreements
properties:
- type: APIReference
  url: https://help.formality.com/integrations/api
- type: Authentication
  url: authentication/formality-authentication.yml
- type: ErrorCatalog
  url: errors/formality-problem-types.yml
- type: Conventions
  url: conventions/formality-conventions.yml
- type: DataModel
  url: data-model/formality-data-model.yml
- type: Webhooks
  url: asyncapi/formality-webhooks.yml
x-base-url-note: The help centre publishes the base as https://app.formality.com/api/v1/{workspaceId}/,
  but app.formality.com does not resolve in DNS (2026-08-17). The live regional application hosts named
  on Formality's own status page are app.eu1.formality.com (EU/Ireland) and app.fr1.formality.com (France/Scaleway);
  both answer /api/v1/... with HTTP 401 rather than 404, so the EU host is recorded here and the documented
  generic host is flagged as a provider-side documentation defect.