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

> ## Agent Instructions
> Reconify's API reference is read-only for customer data. Do not invent endpoints or authentication behavior beyond the OpenAPI contract.
> The public OpenAPI document contains only the documented external /v2 contract.

# Import the API into Postman

> Import the canonical OpenAPI contract instead of maintaining a collection.

Reconify publishes one canonical OpenAPI artifact, so Postman can work from the same
contract this reference documents. No separately maintained collection exists, which means
nothing drifts from the generated spec.

## Import the contract

Three steps take you from the spec URL to a validated key.

<Steps>
  <Step title="Import the OpenAPI URL">
    In Postman, **Import** takes a **Link**:

    ```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
    https://docs.reconifyhq.com/openapi/reconify.openapi.json
    ```

    The option that creates a collection from the specification produces a collection holding
    only the public `/v2` operations.
  </Step>

  <Step title="Set collection authorization">
    The collection's authorization settings take **Bearer Token**. A Postman variable holds
    the key, which keeps it out of individual requests:

    ```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
    Variable: reconify_api_key
    Value: rk_your_key_here
    ```

    The token value then reads `{{reconify_api_key}}`, marked secret wherever your workspace
    supports that control.

    <Warning>
      A real key never syncs into a workspace with broader membership than the Reconify
      organization, and an environment containing it never gets exported or committed.
    </Warning>
  </Step>

  <Step title="Validate the key">
    `GET /v2/events` with `limit=1` is the test, because `GET /v2` and `GET /v2/health` answer
    without checking credentials.

    * `200` confirms the key reads data in its organization.
    * `401` means the key is missing or invalid.
    * `403` means the key is valid but lacks the required access.
  </Step>
</Steps>

## Before you run a write request

Reconify has no sandbox or test mode, and `POST /v2/events` writes immutable evidence to
the organization behind the key. [Send events](/guides/api-integration) covers what a safe
first request looks like.

When the public contract changes, a re-import of the canonical artifact picks it up. The
[versioned manifest](/openapi/manifest.json) carries checksums and version locations for
automated consumers.