Submit a marketing lead
Ingest a contact-form submission from the Devotel landing: marketing-leads ingest. Rejects unsigned or out-of-window submissions (401), malformed payloads (422 VALIDATION_ERROR), and Turnstile failures (422 TURNSTILE_REQUIRED) when the bot-protection gate is armed. On success the lead is persisted and the endpoint replies 201 with { data: { id, status: "received" }, meta }; rate-limited submissions return the standard 429 envelope. This is a public Devotel-property ingest — no caller API key is accepted, and the 503 SERVICE_UNAVAILABLE envelope is returned when the signing secret is not provisioned (the pipeline fails closed).
Authorizations
Dashboard JWT token from Clerk
Headers
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.
1 - 255Sandbox 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.
true, false Body
Contact-form lead, forwarded by the Devotel landing edge. Signed with HMAC-SHA256 over ${timestamp}.${rawBody} (header x-devotel-signature, sha256= prefix allowed), with x-devotel-timestamp within a 300-second window.
Contact-form lead, forwarded by the Devotel landing edge. Signed with HMAC-SHA256 over ${timestamp}.${rawBody} (header x-devotel-signature, sha256= prefix allowed), with x-devotel-timestamp within a 300-second window.
Originating property — e.g. devotel.io-contact, landing-page.
1 - 64The contact's full name.
1 - 200The contact's email address.
320Company or organization name (optional).
200The contact's message body.
1 - 10000UTM attribution captured from the landing session. Any subset of source, medium, campaign, term, content (each ≤ 200 chars).
Visitor user-agent captured at the form edge (optional).
500Visitor referrer URL captured at the form edge (optional).
2000Cloudflare Turnstile token (cf-turnstile-response) solved by the landing form and forwarded inside the signed body. Required when the bot-protection gate is armed server-side; single-use, never persisted.
1 - 2048