Skip to main content
POST
Create Webhook

Overview

Create a new webhook endpoint to receive order, trade, and deposit event notifications. The webhook secret is only returned once at creation, so make sure to store it securely. This endpoint requires Write scope. Store the returned secret immediately; later read responses do not expose it.

Authentication

string
required
Your API key with Write scope

Request Body

string
required
Webhook endpoint URL. It must use HTTPS and resolve to a public internet address.Example: https://example.com/webhooks/daya
array
required
Events to subscribe to (at least one required)Allowed values: order.created, order.filled, order.partially_filled, order.cancelled, order.rejected, trade.executed, deposit.completed, crypto.deposit.completed
string
Optional description for the webhookExample: My order notifications

Request Examples

Response

boolean
required
Indicates if the request was successful
string
required
Human-readable response message
object
required
Created webhook with secret

Success Response

The secret is a 64-character hex string (32 bytes). This is the raw secret used for HMAC-SHA256 signature verification.

Error Responses

Available Events

Important Notes

Store your webhook secret securely! The secret field is only returned once when the webhook is created. If you lose it, you’ll need to rotate the secret.
Webhook URLs must use HTTPS and point to a public internet address. HTTP, localhost, loopback, private-network, link-local, and internal service addresses are rejected.

Rate Limits

  • 100 requests per minute per API key
  • Maximum 5 webhooks per account

Next Steps

Webhook Verification

Learn how to verify webhook signatures

Webhook Events

See event payload details

List Webhooks

View all your webhooks

Update Webhook

Update webhook configuration