Skip to main content
POST
Set a URL to receive webhook notifications for events in your Yativo account. Yativo sends a POST request to your endpoint whenever a matching event occurs and signs every request with an Signature header for verification.
Requires an Idempotency-Key header. To update an existing webhook, send PUT /business/webhook/{webhook} with the webhook ID returned from this endpoint.

Supported Events


Signature Verification

Every webhook delivery includes an Signature header — an HMAC SHA256 hex digest of the raw request body signed with your webhook secret. Algorithm:
Always verify the signature before processing any event. Use constant-time comparison to prevent timing attacks — never a plain string equality check.
Compute the HMAC over the raw request body bytes — not a re-serialized version of parsed JSON. Parsing and re-stringifying can change whitespace or key ordering, causing signature mismatches.

Verification examples

Authorizations

X-Api-Key
string
header
required

Your API key (yativo_pk_...) from Developers → API Keys. Send together with X-Api-Secret.

X-Api-Secret
string
header
required

Your API secret (yativo_sk_...), shown once when the key is created.

Headers

Idempotency-Key
string
required

A unique string per request to ensure idempotent processing.

Body

application/json
url
string<uri>
required

The HTTPS URL of your webhook endpoint. Must be publicly accessible.

Response

201 - application/json

Webhook created

status
string
status_code
integer
message
string
data
object