> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Changelog

> Contract versions and changes to the Living Security Public API.

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`).

* The current specification is always available at
  [`/v1-reference/openapi-v1.json`](/v1-reference/openapi-v1.json).
* Versioned reference snapshots are available at
  `/v1-reference/openapi/<version>.json`, for example
  [`/v1-reference/openapi/2026-07-01.json`](/v1-reference/openapi/2026-07-01.json).

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](/developers/v1/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](/developers/v1/quickstart) for your first request,
[Authentication](/developers/v1/authentication) for API keys and OAuth, and
[Regions](/developers/v1/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](/developers/public-api/overview) for
authentication, pagination, and error handling, and the
[compatibility and deprecation policy](/developers/public-api/overview#compatibility-and-deprecation)
for how this contract evolves.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.