Support

Get help with onelinktoken

One route in, a clear idea of when you'll hear back, and a separate channel for security issues.

Primary route

Contact form

Everything that isn't a security report: integration questions, quota and billing, bug reports, account changes.

Open the form below →

Or email [Support email] directly.

Self-serve

Docs and API reference

Endpoint reference, MCP tool schemas, error codes, and the redeem/revoke flow.

onelinktoken.com/docs →
Security

Vulnerability reports

A separate channel, watched separately. Please do not open a public issue.

[Security contact email]

Send us a message

The form below is the fastest route for anything that isn't a security report. It goes to the same queue as [Support email], so use whichever you prefer — but please read what to include first.

Form not live yet. The embedded form appears here once the repizen publishable key and form id have been provisioned. Until then, email [Support email].

Don't put a raw token value, API key, or password in the form — see never send us a live credential below.

What to include

The more of this we get first time, the fewer round trips it takes. A ticket with the token ID and timestamp usually gets diagnosed on the first reply.

01
Tenant and account → which tenant, which plan
02
Token ID and timestamp (UTC) → never send the raw token value
03
Endpoint or MCP tool called → e.g. create_magic_link, POST /api/v1/tokens
04
What you expected and what happened → status code, error body, request ID if you have one

Never send us a live credential

Don't paste raw token values, API keys, or passwords into a support ticket. We store only a SHA-256 hash of a token, so we can trace everything we need from the token ID alone. If a key has already been exposed, rotate it first, then tell us.

Response times

These are the targets we work to. They are not a contractual service level unless your order form says so.

Kind of request Target first response
Service down or tokens not issuing [Target — e.g. same business day]
Suspected security issue [Target]
Integration or API question [Target]
Billing, quota, or account change [Target]

Support hours: [Support hours and time zone]. Paid plans are answered ahead of free-plan tickets.

Reporting a security issue

Send vulnerability reports to [Security contact email]. Please include enough detail to reproduce the issue, and give us a reasonable window to fix it before disclosing publicly.

Suspect abuse of your account?

Revoke the affected tokens and rotate the tenant API key first — both take effect in under a second — then send us the tenant ID and the time window and we will pull the audit trail for you.

See plans and quotas →