API Authentication

All NadaPay API requests are authenticated using the x-api-key header. This page shows you how to authenticate requests, then walks you through related account, verification, beneficiary, deposit, limit, and provider network tasks.

NadaPay uses one API surface for both sandbox and production. Your API key determines whether requests run in sandbox or production mode, so replace any example URL in this page with your configured NadaPay API base URL.

Get your API key

Log into the NadaPay Dashboard
Navigate to Settings → API Keys
Click Generate Key for the mode you need
Copy the key — it is only shown once

Your key format:

Mode	Prefix
Sandbox	`np_test_`
Production	`np_live_`

Add the header to every request

curl --request GET \
  --url $baseUrl/organizations/accounts \
  --header 'x-api-key: np_test_eda202a11e36xxxxxxxxxxxx'

That's it. Every request to the NadaPay API requires this header.

⚠️
NadaPay uses x-api-key — not Authorization: Bearer. Using the wrong header returns 401 Unauthorized.

Additional how-to guides

Use these task-specific guides for the next step in your integration.

Fetch Organization Accounts

Retrieve your organization accounts, fetch a specific account by ID, and review balances before you fund or execute a transaction.

Check Verification Status

Fetch your current KYC or KYB status and understand what each verification state means.

Create a Beneficiary

Create a beneficiary, then attach a payout account you can reuse in future transaction flows.

Resolve a Bank Account

Validate a bank account and confirm the resolved account name before you add it to a beneficiary.

Get Deposit Instructions

Retrieve the funding details your team or clients need to send money into a NadaPay account.

Fetch Transaction Limits

Check minimum and maximum limits for a currency and country before you execute a transaction.

Get Provider Networks for a Country

Retrieve the available payout networks for a country before you create a beneficiary account.

NadaPay uses x-api-key — not Authorization: Bearer. Using the wrong header returns 401 Unauthorized.

Additional how-to guides

NadaPay uses `x-api-key` — not `Authorization: Bearer`. Using the wrong header returns `401 Unauthorized`.