Download the spec
Same document Mintlify uses to render the interactive playground. You can also request a signed copy from DevRel if you need to pin to a specific version.
Base URLs & auth
All endpoints require HTTPS and bearer tokens. Public clients must follow OAuth 2.1 + PKCE (
code_challenge_method=S256). Service-to-service flows can use confidential client credentials where approved.
Resources at a glance
Each page under OAuth & Consent, Feeds & Access, and Discovery & Health maps directly to an OpenAPI operation. Set the server dropdown (sandbox or production) and hit Try it to execute real requests with your bearer token.
Working with the spec
- Download the JSON file above or fetch it programmatically from
https://docs.humanity.app/api-reference/openapi.json. - Import it into your API tooling. Popular options:
- Postman/Insomnia for manual testing
- Stoplight Studio or VS Code OpenAPI viewers for schema exploration
openapi-generator/orvalif you need a client in another language
- Keep an eye on the
versionfield—Humanity increments it whenever contracts change. DevRel announcements include release notes and deprecation windows.
Authentication reminders
All operations require HTTPS and a valid access token. If you call the endpoints outside the SDK:- Read the OAuth section of the Quickstart to mint tokens with PKCE.
- Send
Authorization: Bearer <access_token>headers on every request. - Provide
Humanity-Client-Id(optional) when you need explicit attribution across multiple client IDs.
security block mirrors these requirements so generators and lint rules can enforce them automatically.