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

# Contact & support

> How to get an api_secret, reach the Synthpop team, and report an API issue.

## Get an api\_secret

Every call to the API is authenticated, so the first thing any integration needs
is an **`api_secret`**. Access is provisioned per organization.

<Steps>
  <Step title="Have an admin generate it in the Synthpop UI">
    An administrator in your organization signs in to
    [app.synthpop.ai](https://app.synthpop.ai/) and generates (or resets) the
    `api_secret` for the environment you're integrating with. Staging and
    production have **separate** secrets.
  </Step>

  <Step title="No account yet? Request access">
    If your organization isn't provisioned for API access yet — or you don't have
    UI access or a Synthpop contact — request access through the
    [contact form](https://www.synthpop.ai/contact-us). If you already have a
    Synthpop representative, reach out to them directly; either way they'll issue
    an `api_secret` and confirm which `task_type` values are enabled for you.
  </Step>

  <Step title="Store it safely">
    Synthpop does not store the secret after it's shown, and generating a new one
    immediately invalidates the previous one. Keep it server-side, never commit
    it, and exchange it for a bearer token rather than sending it on
    every request. See [Authentication](/authentication).
  </Step>
</Steps>

<Note>
  `task_type` is provisioned during onboarding — there is no endpoint that lists
  the types available to you. Your Synthpop contact tells you which are enabled.
</Note>

## Reach the Synthpop team

<CardGroup cols={2}>
  <Card title="Contact Synthpop" icon="envelope" href="https://www.synthpop.ai/contact-us">
    Get in touch about access, onboarding, provisioning a new `task_type`, or
    enabling callbacks and auto-read for your organization.
  </Card>

  <Card title="Your Synthpop contact" icon="user-headset">
    Already integrating? Your dedicated Synthpop representative or customer
    success contact is the fastest path for account-specific questions.
  </Card>
</CardGroup>

## Report an API issue

When something isn't working as documented, share the details below so the team
can trace it quickly. **Never include an `api_secret` or a bearer token** in a
report.

<Steps>
  <Step title="Identify the environment and endpoint">
    State whether you hit **staging** (`stage.synthpop.ai`) or **production**
    (`app.synthpop.ai`), and the exact endpoint and method (for example
    `POST /task/create`).
  </Step>

  <Step title="Include the Task identifiers">
    Provide the Task's Synthpop `uuid` and/or your `external_id`. These let the
    team locate the exact Task without any credentials.
  </Step>

  <Step title="Include timing and the response">
    Add an approximate timestamp (with timezone), the HTTP status code you
    received, and the response body — redacting any sensitive content.
  </Step>

  <Step title="Describe expected vs. actual">
    Say what you expected and what happened instead. If it's reproducible,
    include the minimal request that triggers it.
  </Step>
</Steps>

<Warning>
  Do not paste secrets, bearer tokens, or patient information into a support
  request. The Task `uuid` / `external_id`, environment, endpoint, timestamp, and
  status code are enough for the team to investigate.
</Warning>

## Before you reach out

Many questions are already answered in the docs:

<CardGroup cols={2}>
  <Card title="FAQ" icon="circle-question" href="/support/faq">
    Access, environments, async results, file types, limits, and SDKs.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/guides/errors">
    Status codes and error bodies, with what each one means.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    The `api_secret` format, token exchange, and the default-deny model.
  </Card>

  <Card title="Async results" icon="clock" href="/guides/async-results">
    Polling, callbacks, and the `waiting` status.
  </Card>
</CardGroup>