Skip to main content

Email

sricharan.rayala@dotportion.com

Discord

Quick questions and integration help.

Sales

Plans, limits and enterprise requirements.

API reference

Try the request in the playground first — it often answers the question.

​
Reporting an API problem

Include these four things and we can usually find it immediately:
1

The request id

From meta.request_id, error.request_id, or the X-Request-Id header. This is the single most useful thing you can send — it locates your exact request in our logs.
2

Method and path

For example POST /v1/assessments/{id}/invitations. Redact ids if you’d rather, but keep the shape.
3

What you expected, and what you got

Including the status code and the error.code.
4

Whether it was a live or test key

Just the environment — never send the key itself. If a key has been exposed anywhere, revoke it in Settings → API keys first; that takes effect immediately.
Don’t paste an API key into an email, a Discord message, or a GitHub issue. If you already have, revoke it and mint a replacement — a leaked key can read every candidate report in your workspace.

​
Before you write in

A few things that look like bugs and usually aren’t:

​
Reporting a security issue

Email sricharan.rayala@dotportion.com directly rather than opening a public issue or posting in Discord. Include the request id and enough detail to reproduce it. If it involves a key or token, revoke it first.