Skip to main content
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

1

Open Postman's import dialog

In Postman, select Import in the top-left and select the Link tab.
2

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

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.
Prefer a file? Download meridian.postman_collection.json and use Import → File instead.

​
Variables

VariableDescription
baseUrlAPI base URL. Defaults to the sandbox host; override per environment when you’re ready for production.
meridianApiKeyYour Meridian API key.
meridianApiSecretYour Meridian API secret. Used only to compute the request signature — it is never sent on the wire.
meridianProgramIdYour Meridian Program ID. Required for Meridian Accounts and Payout Origination.
meridianUserIdThe Meridian user the call targets. Required for Meridian Accounts MULTI_USER integrations; leave blank for SINGLE_USER.
meridianAccessTokenPopulated automatically after a successful call to POST /v1/auth/token. Use {{meridianAccessToken}} in any request that needs a bearer token.
meridianRefreshTokenPopulated automatically after a successful call to POST /v1/auth/token. Picked up automatically by the Refresh Token request.
Sandbox and production credentials are different. Do not reuse them across environments.

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