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

# Choose the right Daya API

> Choose an API, follow its quickstart, and build your first working integration.

Start with what you want to build. You only need to learn the API that fits your use case.

> [!NOTE]
>
> **The Business API documentation is under the “Daya API” tab.**

## 1. Choose your API

| What you want to build | API and quickstart |
| - | - |
| Receive payments, create customer funding accounts, or send bank payouts | [**Business API**](/quickstart) |
| Trade currencies with market or limit orders | [**Pro API**](/pro/quickstart) |
| Let users buy, sell, and hold supported crypto assets | [**Coins API**](/coins/quickstart) |
| Let users trade supported stock instruments and track their investments | [**Stocks API**](/stocks/quickstart) |

### Know these differences before choosing

* **Business:** An onramp converts NGN to supported stablecoins; an offramp converts supported stablecoins to NGN. Creating a funding account gives the customer payment instructions—it does not mean money has arrived. Track the deposit separately. Bank payouts and crypto wallet withdrawals use different flows.
* **Pro:** This is currency trading, not the Business payments API. A limit order lets you choose your trading price. New dashboard keys do not currently support Pro withdrawals; confirm your cash-out options with Daya before integrating.
* **Coins:** Buying crypto does not send it to an external wallet. That needs a separate withdrawal after the purchase completes. Check which assets and networks support withdrawals, including fees and minimums.
* **Stocks:** Check market hours, asset eligibility, and ownership disclosures. Some instruments give exposure to price movements, not direct share ownership. Follow the [instrument guidance](/stocks/partner-integration) when explaining this to customers.

## 2. Connect and make your first request

1. Open your chosen API's quickstart above.
2. Follow its authentication guide to set up access and select the required API-key permissions: [Business](/authentication), [Pro](/pro/authentication), [Coins](/coins/authentication), or [Stocks](/stocks/authentication).
3. Follow the quickstart's example before building your full payment or trading flow.

> [!WARNING]
>
> Business has a sandbox for testing. The public Pro, Coins, and Stocks APIs are production-only. Do not send test payments or test trades to live endpoints.

## 3. Build the complete flow

Read your product's partner guide for funding, transactions, status tracking, and recovery:

* [Business Partner Integration](/partner-integration)
* [Pro Partner Integration](/pro/partner-integration)
* [Coins Partner Integration](/coins/partner-integration)
* [Stocks Partner Integration](/stocks/partner-integration)

An accepted request is not a completed payment or trade. Follow the guide's status checks and webhooks before telling a customer it succeeded. A **webhook** is a notification Daya sends to your server when something changes.

## 4. Check balances and launch requirements

* **Product balances are separate.** A shared API key does not move funds between Business, Pro, Coins, and Stocks.
* **Track each customer's money.** Business has customer-linked funding flows. Coins and Stocks record your business's combined balances and holdings; your app must track each customer's share. Pro also has an account-level balance: if you serve multiple customers, track their shares yourself and reconcile the totals with Daya. See the [Coins](/coins/integration-model), [Stocks](/stocks/integration-model), and [Pro](/pro/partner-integration) integration guides.
* **Confirm availability before launch.** Check your chosen API's verification requirements, supported assets, fees, limits, and withdrawal options. Features in one API are not automatically available in another.

Not sure which API fits? Tell [Daya support](mailto:support@daya.co) what the customer pays with, what they should receive, and whether the funds belong to your business or individual customers.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.