Skip to main content
The Living Security API v1 Postman collection is generated from the same OpenAPI spec that powers the API v1 Reference, so it always matches the published contract. It covers every /v1 operation, grouped by resource, with authentication preconfigured.

​
Download

The download links prompt you to sign in with your Living Security account before the file is served.

Living Security API v1 collection

Postman Collection v2.1 with all /v1 operations and Basic auth preconfigured. Collection baseUrl is blank — select a regional environment before you send a request.Download the collection

Production (US) environment

baseUrl preset to https://api.us-east-1.livingsecurity.ai/v1, with empty apiKeySecret and contractVersion variables to fill in.Download the US production environment

Production (EU) environment

baseUrl preset to https://api.eu-west-1.livingsecurity.ai/v1, with empty apiKeySecret and contractVersion variables to fill in.Download the EU production environment

Environment template

The same variables with a blank baseUrl, for non-production setups.Download the environment template

​
Set up in Postman

1

Import the files

In Postman, choose Import and drop in the collection file plus the Production (US) or Production (EU) environment that matches the organization. See Regions.
2

Create an API key

In the Dashboard, open Settings → Integrations & Developers → Developer Hub, create a service account, and create an API key. The key secret starts with lsk_live_ and is shown once — copy it immediately. See API keys for details.
3

Paste the secret

Set the apiKeySecret variable — either in the imported environment (recommended; it is a secret-type variable) or in the collection’s Variables tab.
4

Send a request

Select the imported regional environment, open any request — for example Organization → Retrieve the organization — and hit Send. Do not send until an environment is selected; the collection baseUrl is blank on purpose.

​
How authentication is preconfigured

The collection sets Basic auth at the collection level with username apikey and password {{apiKeySecret}}. The API accepts the key secret in either Basic auth field, so this works as-is once the variable is set. If you prefer bearer authentication, change the collection’s Authorization type to Bearer Token and use {{apiKeySecret}} as the token — the API accepts the same secret both ways. Using a Bearer header with an API key does not require OAuth. To use OAuth, set Bearer Token to your OAuth access token instead of the API key secret. See Authentication to choose a method and OAuth client credentials for token and client setup.

​
Contract version header

Every request carries a Living-Security-Version header preset to {{contractVersion}}, disabled by default. Leave it disabled to use your organization’s pinned contract version. Enable it to pin the request to a specific published version — see the changelog for published versions.

​
Query parameters and bodies

List-endpoint filters (limit, page_token, and resource-specific filters) are included on each request but disabled, so a fresh import calls every endpoint successfully. Enable and fill the ones you need — see Pagination for how page_token works. Request bodies on POST operations are prefilled with typed placeholder values.
The collection is regenerated from the published OpenAPI spec on every contract change — download a fresh copy rather than editing requests you want to keep current.