Skip to main content
Live only for now. Stocks does not have a sandbox yet — every request runs against the live environment with real balances and real money. Sandbox keys (sk_sandbox_...) are not accepted, and the dashboard’s sandbox mode shows a notice instead of Stocks data. Sandbox support is on the way.

The shared key model

Stocks is an extension of the Daya API, so it does not have its own key-issuance flow. You authenticate Stocks requests with the same Daya API key you use for the rest of the Daya API — the same key, the same header, the same dashboard.
Issue and manage your Daya API keys in the Daya dashboard. When you create or edit a key, grant it the Stocks scopes your integration needs. There is no separate Stocks key to request.
Send the key in the X-API-Key header on every request:

Stocks scopes

A Daya API key carries scopes. To call Stocks endpoints, the key must include the matching Stocks scope:
stocks:withdraw authorizes fund movement off the platform. Only attach it to keys stored in trusted server-side systems.

Making an authenticated request

Error responses

Stocks uses the standard Daya response envelope: { success, message?, data?, error?, timestamp }.

401 Unauthorized

Missing or invalid API key:

403 Forbidden

The key is valid but is missing the required Stocks scope:

Next steps

Quickstart

Your first authenticated call, end to end.

Concepts

Balances, quotes, orders, and withdrawals.