> ## 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.

# Postman collection

> Import the generated Living Security Public API Postman collection, paste an API key, and call /v1 in minutes.

The Living Security API v1 Postman collection is generated from the same
OpenAPI spec that powers the [API v1 Reference](/v1-reference/openapi-v1.json),
so it always matches the published contract. It covers every `/v1` operation,
grouped by resource, with authentication preconfigured.

## Download

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

<CardGroup cols={1}>
  <Card title="Living Security API v1 collection" icon="download">
    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.

    <a href="/v1-reference/postman/living-security-api-v1.postman_collection.json" download="living-security-api-v1.postman_collection.json">Download the collection</a>
  </Card>

  <Card title="Production (US) environment" icon="download">
    `baseUrl` preset to `https://api.us-east-1.livingsecurity.ai/v1`, with
    empty `apiKeySecret` and `contractVersion` variables to fill in.

    <a href="/v1-reference/postman/living-security-production.postman_environment.json" download="living-security-production.postman_environment.json">Download the US production environment</a>
  </Card>

  <Card title="Production (EU) environment" icon="download">
    `baseUrl` preset to `https://api.eu-west-1.livingsecurity.ai/v1`, with
    empty `apiKeySecret` and `contractVersion` variables to fill in.

    <a href="/v1-reference/postman/living-security-production-eu.postman_environment.json" download="living-security-production-eu.postman_environment.json">Download the EU production environment</a>
  </Card>

  <Card title="Environment template" icon="download">
    The same variables with a blank `baseUrl`, for non-production setups.

    <a href="/v1-reference/postman/living-security-environment-template.postman_environment.json" download="living-security-environment-template.postman_environment.json">Download the environment template</a>
  </Card>
</CardGroup>

## Set up in Postman

<Steps>
  <Step title="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](/developers/v1/regions).
  </Step>

  <Step title="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](/developers/developer-hub/api-keys) for details.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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](/developers/v1/authentication) to choose a method and
[OAuth client credentials](/developers/v1/oauth) 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](/developers/v1/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](/developers/v1/pagination) for how `page_token` works. Request
bodies on `POST` operations are prefilled with typed placeholder values.

<Note>
  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.
</Note>


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