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

# Request API access

> Name your key, request sandbox or live — Super Admin approves (not self-serve).

## Before you start

* An Ondial account that can log into the dashboard
* A place to store secrets (env / secret manager)

## Steps

<Steps>
  <Step title="Sign in">
    Open `https://dashboard.ondial.ai` and sign in with the account that will own campaigns.
  </Step>

  <Step title="Open API Access">
    Go to **Dashboard → API Access** (or **Settings → API Access**).
  </Step>

  <Step title="Submit a request">
    1. Enter a **key name** (e.g. `Production CRM`, `Staging Zoho`) so you can tell keys apart later.
    2. Add a short **why** note for your admin.
    3. Choose **Test mode (Sandbox)** or **Live**.
    4. Submit. Status becomes `pending_request`.

    You can **rename** a key later from the same page without rotating the secret.
  </Step>

  <Step title="Super Admin approves">
    Ops approves in **Super Admin → API Keys**. They see your **key name**, mode, and reason. The plaintext secret is shown **once** (`ond_test_…` or `ond_live_…`).
  </Step>

  <Step title="Store the key">
    ```bash theme={"system"}
    export ONDIAL_BASE_URL="https://dashboard.ondial.ai"
    export ONDIAL_API_KEY="ond_test_xxxxxxxx"
    ```
  </Step>

  <Step title="Verify">
    Call [Ping](/api-reference/endpoint/core/ping) or:

    ```bash theme={"system"}
    curl -sS -H "Authorization: Bearer $ONDIAL_API_KEY" \
      "$ONDIAL_BASE_URL/api/v1/ping"
    ```
  </Step>
</Steps>

<Note>
  Tenants cannot create live keys themselves. Revoked keys return `401`. Global kill switch returns `503 api_globally_disabled`. The dashboard only stores a hash of the secret — use **Rotate** if you lose it.
</Note>