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

# Postman collection

> Import the official Meridian Postman collection. HMAC signing is handled for you — set your credentials and start making requests.

Meridian publishes a Postman collection that covers Meridian Accounts, Payout Origination, and Retail Virtual Accounts. Signing is handled for you, so once your credentials are set you can call any endpoint immediately.

## Import

<Steps>
  <Step title="Open Postman's import dialog">
    In Postman, select **Import** in the top-left and select the **Link** tab.
  </Step>

  <Step title="Paste the collection URL">
    Paste this URL and select **Continue**, then **Import**:

    ```
    https://download.mnai.com/postman/meridian.postman_collection.json
    ```

    The collection appears in your sidebar as **Meridian API**, with one folder per product.
  </Step>

  <Step title="Store your credentials in a Postman Environment">
    Create a new **Environment** (left sidebar → Environments → **+**) called something like `Meridian sandbox`. Add the variables listed below and fill in your credentials there. Make the environment active using the dropdown in the top-right.

    Storing credentials in an Environment (rather than on the collection) means re-importing later won't wipe them.
  </Step>
</Steps>

<Note>
  Prefer a file? Download
  [`meridian.postman_collection.json`](https://download.mnai.com/postman/meridian.postman_collection.json)
  and use **Import → File** instead.
</Note>

## Variables

| Variable               | Description                                                                                                                                       |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `baseUrl`              | API base URL. Defaults to the sandbox host; override per environment when you're ready for production.                                            |
| `meridianApiKey`       | Your Meridian API key.                                                                                                                            |
| `meridianApiSecret`    | Your Meridian API secret. Used only to compute the request signature — it is never sent on the wire.                                              |
| `meridianProgramId`    | Your Meridian Program ID. Required for Meridian Accounts and Payout Origination.                                                                  |
| `meridianUserId`       | The Meridian user the call targets. Required for Meridian Accounts MULTI\_USER integrations; leave blank for SINGLE\_USER.                        |
| `meridianAccessToken`  | Populated automatically after a successful call to `POST /v1/auth/token`. Use `{{meridianAccessToken}}` in any request that needs a bearer token. |
| `meridianRefreshToken` | Populated automatically after a successful call to `POST /v1/auth/token`. Picked up automatically by the Refresh Token request.                   |

<Info>
  Sandbox and production credentials are different. Do not reuse them across environments.
</Info>

## Troubleshooting

If a request fails with `401 Unauthorized`, the most common causes are:

* An incorrect or missing `meridianApiSecret`
* Clock skew greater than 60 seconds between your machine and Meridian
* Using sandbox credentials against production (or vice versa)
* A `meridianProgramId` mismatch for the targeted product

## Updates

The collection is updated automatically when the API changes. To pull the latest version, re-run the import from the same URL — Postman will offer to **Replace** the existing collection.

<Warning>
  Re-importing replaces the collection and resets any values you stored directly on it. Keep your credentials in a Postman Environment to avoid having to re-enter them.
</Warning>