Retrieve the internal accounts available to your NadaPay organization so you can fund, reconcile, quote, and execute transactions.

⏱️
Time to integrate: This is usually the first endpoint you should call. Most teams can validate it in under 5 minutes once their x-api-key and base URL are configured.

What this endpoint does

Use this endpoint to fetch all accounts that belong to the authenticated organization.

These accounts represent the internal balances or ledgers your organization can use for:

funding workflows
balance checks
transaction preparation
reconciliation
selecting the source account for a live transaction

When to call this endpoint

Call this endpoint when you need to:

confirm that your API key is working
see which accounts are available to your organization
identify the correct account before generating a quote or executing a transaction
verify that your organization has been provisioned in the expected environment

For most teams, this should be the first operational API call after authentication is configured.

Authentication

Send your API key in the x-api-key header on every request.

Item	Value
Authentication method	API key
Required header	`x-api-key`
Rate limit scope	Per API key

Fastest path to success

Use this endpoint first, then continue with the core integration flow:

Fetch organization accounts.
Check verification status.
Create a beneficiary.
Add a beneficiary account or resolve bank details.
Generate a quote.
Execute a transaction.

How to use the response

Use the returned account records to determine:

which account IDs belong to your organization
which currencies are available
which account you should use for a specific flow
whether an account appears active and ready for use

You will typically store the account ID in your backend so later steps can reference the correct source account.

Common uses for returned account data

select the funding source for a transaction
display available accounts in an internal operations dashboard
reconcile balances across environments
verify that the expected wallet or ledger exists before launch

What to verify in the response

After your first successful call, confirm these points:

the response includes the accounts you expect for this organization
the environment is correct for the credentials you used
the currencies shown match your onboarding and treasury expectations
the account status appears usable for your planned flow

⚠️
Needs confirmation: The exact response schema, account status values, currency field names, and whether pagination applies should be confirmed in the underlying API definition.

Production notes

Before you use an account in a live workflow:

Confirm the account belongs to the correct production organization.
Confirm the account supports the currency required for the transaction.
Confirm the account has sufficient balance before executing a transaction.
Log the account ID you select for traceability and audit review.

This endpoint is also useful as a launch-day validation check because it confirms both authentication and account provisioning.

Common failure cases

Authentication fails

Check these items first:

the x-api-key header is present
the API key belongs to the intended environment
the key has not expired, been rotated, or been revoked
the request is going to the correct base URL

The response is empty or missing expected accounts

Check these items next:

you are using the correct organization credentials
you are not mixing sandbox and production environments
the organization has completed the required onboarding steps
the account provisioning for this environment is complete

Requests fail under load

Because rate limits are enforced per API key:

avoid unnecessary polling
cache account metadata when appropriate
add backoff for retries
separate background synchronization from user-triggered workflows when possible

⚠️
Needs confirmation: Exact error codes, rate limit headers, and retry recommendations are not yet documented on this page.

Recommended next endpoints

After you fetch accounts, continue with:

Enterprise implementation notes

Logging and auditability

Record these values where available:

account ID
organization ID
request timestamp
internal service or user initiating the request

Environment separation

Keep sandbox and production account IDs separate. Do not assume an account identifier from one environment exists in the other.

Access control

Limit which internal services can read account data in production, especially if your account inventory is used for treasury or operational workflows.

Troubleshooting checklist

Use this checklist if this endpoint does not behave as expected:

Verify the request uses x-api-key.
Verify the key matches the intended environment.
Verify the base URL is correct.
Verify the organization has been provisioned and approved for the environment.
Verify you are checking the right organization if your team manages multiple entities.

Related pages

Getting Started

Use this endpoint as your first successful API call.

Onboard with us

Confirm account provisioning and verification progress during onboarding.

Going Live

Use account retrieval and balance checks as part of your production launch checklist.

200List of financial accounts and their current balances.