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

# Postman Collection

> Test the Zentra API without writing code

Explore and test the Zentra API using the checked-in Postman collection in this repo. The collection is broader than the reviewed public gateway surface, so use it together with [Reviewed Public Surface](/resources/reviewed-public-surface) when choosing which folders to rely on in production.

## Collection Files

<CardGroup cols={1}>
  <Card title="Reviewed surface policy" icon="shield-check" href="/resources/reviewed-public-surface">
    Use this alongside the collection so you can separate reviewed public endpoints from compatibility or draft folders.
  </Card>
</CardGroup>

Import the checked-in files from the repo:

* `docs/current/api-specs/postman/zentra-api.postman_collection.json`
* `docs/current/api-specs/postman/environments/zentra-sandbox.postman_environment.json`
* `docs/current/api-specs/postman/environments/zentra-production.postman_environment.json`

## Getting Started

### 1. Import Collection

Open Postman, click **Import**, then upload the checked-in collection and environment files listed above.

### 2. Configure Environment

The collection includes a `Zentra Sandbox` environment. You need to set your API keys:

1. Select **Zentra Sandbox** from the environment dropdown
2. Click the **Eye icon** (Environment quick look)
3. Click **Edit**
4. Paste your keys from the [Developer Console](https://api.usezentra.com/developer/signin?callbackUrl=%2Fdeveloper%2Fapi-keys):
   * `secretKey`: `sk_sandbox_...`
   * `publishableKey`: `pk_sandbox_...`
   * `baseUrl`: `https://sandbox.api.usezentra.com`

### 3. Make a Request

Start with a reviewed primitive request:

1. Open **Transfers** > **Resolve Account**
2. Click **Send**
3. You should see a `200 OK` response with resolved bank-account details

## Collection Features

* **Auth Helper**: Automatically adds your Bearer token to headers
* **Chained Requests**: `{{reference}}` from a transaction is automatically saved to environment variables for the next verification step
* **Examples**: Every endpoint includes success and error response examples
* **Documentation**: Inline description of fields and parameters

<Warning>
  The checked-in collection still contains compatibility and draft folders such as customers, wallets, analytics, plans, or subscriptions. Those folders are useful for tenant-specific overlays, but they are not proof of reviewed public support.
</Warning>

<Tip>
  Use the "Pre-request Script" tab to generate unique references (`ORD_{{$timestamp}}`) automatically for testing.
</Tip>