Skip to main content
AI coding assistants can help you move faster with the Daya API when you give them the right docs, workflow context, and safety boundaries. Use this page to give tools like Claude Code, Cursor, Codex, GitHub Copilot, and ChatGPT enough context to explain Daya concepts, generate integration code, write tests, and debug API or webhook issues.
Do not paste production API keys, secrets, private credentials, customer data, wallet private keys, or sensitive financial information into AI assistants. Use sandbox credentials and test data while developing.

​
Start with these resources

Share the most relevant Daya docs with your AI assistant before asking it to generate or edit code.

Quick Start

Create your first onramp or offramp and track the first deposit.

Authentication

Learn how to authenticate requests with API keys and idempotency keys.

Core Concepts

Understand funding accounts, deposits, transfers, rates, and settlement.

Sandbox Testing

Test Daya flows safely before moving money in production.

Webhooks

Receive real-time event notifications from Daya.

Funding Accounts API

Reference the primary endpoint for creating onramp and offramp flows.
If you are building with Daya Pro, also share the Daya Pro overview, Daya Pro authentication guide, and the relevant Daya Pro endpoint docs.
1

Choose the Daya flow you are building

Be specific about whether you are creating customers, funding accounts, onramps, offramps, transfers, USD virtual accounts, webhooks, or Daya Pro trading flows.
2

Share the relevant docs

Give your assistant links to the quickstart, authentication guide, and the specific endpoint or concept pages for your flow.
3

Ask the assistant to inspect your project first

Have it identify your language, framework, existing API client patterns, environment variable conventions, and test setup before it writes code.
4

Build against sandbox

Use sandbox API keys, sandbox base URLs, test data, and simulated flows until your integration is ready for production.
5

Request tests and production checks

Ask for request validation, idempotency handling, webhook signature verification, retries, logging, and error handling.

​
Use with AI coding assistants

Open your project in Codex, share the relevant Daya docs links, then ask Codex to inspect your codebase before making changes.A good starting prompt:
I am integrating the Daya API into this project. Read the Daya quickstart, authentication guide, core concepts, and relevant endpoint docs. First inspect the codebase and explain the best integration point. Then propose the smallest implementation plan before editing files.

​
Example prompts

​
Explore the API

I am building with the Daya API. Read the Daya quickstart, authentication guide, core concepts, and relevant endpoint docs. Explain the main Daya resources, the authentication model, the sandbox environment, and the recommended first integration path.

​
Generate an integration

Using the Daya API docs, generate a [language/framework] implementation for [specific workflow]. Include authentication, idempotency for write requests, request validation, typed responses, error handling, and a simple test.

​
Create a funding account

Help me implement a Daya funding account flow for [onramp/offramp]. Use the sandbox base URL, keep the API key in an environment variable, include an X-Idempotency-Key header, and show how to store the returned funding_account id.

​
Implement webhooks

Help me implement Daya webhook handling in [framework]. Include signature verification, idempotent event processing, structured logging, retry-safe behavior, and tests for valid and invalid signatures.

​
Debug an API error

I am calling the Daya API and getting this error: [paste sanitized error response]. Based on the Daya docs, explain the likely cause, the smallest fix, and what I should log or test to confirm it.

​
Review an integration

Review this Daya integration for correctness, security issues, missing idempotency, missing webhook verification, weak error handling, sandbox/production mixups, and production readiness.

​
What to include in your prompt

The more precise your prompt, the better your assistant’s output will be.
IncludeExample
Workflow”Create an onramp funding account and reconcile deposits”
Runtime”Node.js 20 with Express”
Environment”Sandbox only”
Daya docs”Quickstart, authentication, webhooks, and endpoint docs”
Existing code context”Use the existing API client in src/lib/api.ts”
Safety requirements”No production keys, no customer data, add tests”

​
Common Daya tasks for AI assistants

Ask your assistant to help with focused tasks instead of broad, open-ended requests.
Ask the assistant to create a small client that reads DAYA_API_KEY and DAYA_BASE_URL from environment variables, sends the X-Api-Key header, and returns structured errors.
Ask the assistant to add an X-Idempotency-Key header for create or transfer requests and explain when the same key should be reused.
Ask the assistant to use https://api.sandbox.daya.co, fake customer data, and sandbox-only keys while implementing and testing the first flow.
Ask the assistant to implement Daya webhook signature verification before any event processing logic runs.
Ask the assistant to check for missing logs, retries, idempotency, environment separation, test coverage, and secret handling.

​
Security checklist

Before you paste context into an AI assistant or accept generated code, check that:
  • Production API keys and webhook secrets are not included in prompts
  • Customer personal information and sensitive financial data are removed
  • API keys are loaded from environment variables or a secret manager
  • Sandbox and production base URLs are clearly separated
  • Write requests use idempotency keys where required
  • Webhook handlers verify signatures before trusting event payloads
  • Logs do not include full secrets, private credentials, or sensitive customer data

​
Next steps

Create your first flow

Start with the Daya quickstart.

Review authentication

Learn how API keys and idempotency keys work.

Test in sandbox

Validate your integration before production.

Set up webhooks

Receive and verify Daya events.