> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dotportion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to get help with the API, and what to include so we can actually diagnose it.

<CardGroup cols={2}>
  <Card title="Email" icon="envelope" href="mailto:sricharan.rayala@dotportion.com">
    [sricharan.rayala@dotportion.com](mailto:sricharan.rayala@dotportion.com)
  </Card>

  <Card title="Discord" icon="discord" href="https://discord.gg/Ewp2uPG534">
    Quick questions and integration help.
  </Card>

  <Card title="Sales" icon="phone" href="https://www.dotportion.com/contact/sales">
    Plans, limits and enterprise requirements.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference">
    Try the request in the playground first — it often answers the question.
  </Card>
</CardGroup>

## Reporting an API problem

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="Method and path">
    For example `POST /v1/assessments/{id}/invitations`. Redact ids if you'd rather, but
    keep the shape.
  </Step>

  <Step title="What you expected, and what you got">
    Including the status code and the `error.code`.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Warning>
  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.
</Warning>

## Before you write in

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

| Symptom                                     | Likely cause                                                                    |
| ------------------------------------------- | ------------------------------------------------------------------------------- |
| `404` on an id you can see in the dashboard | The key belongs to a team-scoped member. See [Teams & roles](/teams-and-roles). |
| `403` from a `write` key                    | The creating member's role can't perform that action, separately from scope.    |
| Report has `ship_score: null`               | Grading hasn't finished. Check `evaluated`.                                     |
| A pillar `score` is `null`                  | Not enough evidence for that area — render as "not enough data", not zero.      |
| `percentile` key missing entirely           | Omitted until the comparison population is large enough. Check for the key.     |
| `workspace_archive_url` is `null`           | Nothing submitted yet, or a test-mode key (always `null` there).                |
| A write "worked" but nothing changed        | You used a `sk_test_` key. Test mode is stateless by design.                    |

## Reporting a security issue

Email **[sricharan.rayala@dotportion.com](mailto: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.