Operational playbooks live next to product surfaces.

Start with docs for precision, escalate through Helpdesk when logs or account state matter, loop sales when procurement needs a human.

SUCCESS

Authenticated channels exist so we never ask you to paste secrets into email—rotate keys when in doubt.

Jump to the right surface

Helpdesk (signed in)

Tickets preserve threading, prioritize regressions with traces, and keep sensitive context out of public inboxes.

Launch Helpdesk

API documentation

Interactive references for routes, payloads, webhook signatures, idempotency expectations, and environment toggles.

Browse API docs

Commercial questions

Pricing, onboarding scope, timelines, procurement packs—ideal before you finalize architecture reviews.

Contact

Before opening a ticket

Capture request IDs, timestamps, and webhook delivery attempts when debugging integrations.
Sanitize pasted payloads—never share bearer tokens or signing secrets publicly.
Verify whether behavior reproduces against `sk_test_` endpoints to isolate environmental issues.
Summarize attempted remediation so support avoids redundant loops.

Severity framing

Production-impacting incidents with widespread failures warrant urgent Subject lines plus recent changes on your side (releases, rotations, infra). Narrow cosmetic issues still matter—expect reasonable SLAs keyed to plan tier.

Back to home