Skip to main content
POST
Meta data-deletion callback

Authorizations

Authorization
string
header
required

Dashboard JWT token from Clerk

Headers

Idempotency-Key
string

Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.

Required string length: 1 - 255
X-Test-Mode
enum<string>

Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.

Available options:
true,
false

Body

application/x-www-form-urlencoded
signed_request
string
required

Meta signed_request: base64url(HMAC-SHA256(signature)) + '.' + base64url(JSON payload)

Required string length: 20 - 8192

Response

Deletion request accepted — returns the confirmation URL and code.

Deletion request accepted — returns the confirmation URL and code.

url
string
required

Public confirmation page where the requester can track deletion progress.

Example:

"https://orbit.devotel.io/legal/data-deletion?id=Ab1Cd2EfGh3J"

confirmation_code
string
required

The code Meta must echo back to the requester; also usable with GET /status/{code}.

Example:

"Ab1Cd2EfGh3J"