Skip to main content
The Living Security Public API uses date-based contract versions (YYYY-MM-DD). The published OpenAPI document embeds its contract version as info["x-contract-version"], and each operation declares its lifecycle stage as x-lifecycle-stage (preview, compatibility, or ga). Additive, backwards-compatible changes (new operations, new optional fields) ship within the current contract version. A new contract version is published only for breaking changes, together with an entry on this page describing the change and the migration path.

​
Documentation updates

2026-08-25 — The /v1 guides and OpenAPI servers list now name the live US and EU regional hosts. This is a documentation clarification. The contract version is unchanged. See Regions.

​
2026-07-01

The /v1 Public API supports this contract version. Pin it using Living-Security-Version: 2026-07-01, or use the default version assigned to your service account. See the API quickstart for your first request, Authentication for API keys and OAuth, and Regions for the correct host.

​
2026-08-05

This date identifies the separate legacy /api/v1 compatibility contract. It is not a Living-Security-Version value for the new /v1 API.
  • People: search organization people (GET /people/search) and retrieve a person’s membership (GET /people/{personId}/membership).
  • API access keys: create, list, rotate, and revoke API access keys (POST /access-keys, GET /access-keys, POST /access-keys/{id}/rotate, DELETE /access-keys/{id}).
All operations in this version are published at the compatibility lifecycle stage. See the Public API overview for authentication, pagination, and error handling, and the compatibility and deprecation policy for how this contract evolves.