Getting Started

This guide walks you through setting up your organization on Taiga — from invite-only portal access to submitting your first session.

1. Get invited

Partner Portal access is invite-only. Ask your Taiga contact to onboard a partner admin for your organization. They will send you:

• Your portal sign-in URL
• A temporary password
• Confirmation that your partner organization is active

After that, sign in at partner.usetaiga.com/sign-in.

2. Create an API key

Navigate to API Keys in the portal and click New Key.

• Give it a descriptive label (e.g. "Production", "Staging").
• Copy the key immediately — it's shown only once.
• Store it securely in your backend environment variables.

API keys use the format tga_live_... and are 80 characters long. The first 16 characters (the prefix) are visible in the portal for identification.

You can create multiple keys (e.g. separate keys for staging and production) and revoke any key at any time.

3. Onboard providers

Each therapist needs to be registered before you can submit sessions on their behalf. Provider onboarding happens through the API:

curl -X POST https://api.usetaiga.com/api/v1/partner/providers \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": {
      "firstName": "Jane",
      "lastName": "Smith",
      "npi": "1234567890"
    },
    "practice": {
      "name": "Smith Therapy Associates",
      "taxId": "123456789",
      "address": {
        "street": "100 Main St",
        "city": "New York",
        "state": "NY",
        "zip": "10001"
      }
    }
  }'

Provider onboarding is idempotent on NPI — calling it again with the same NPI returns the existing record. See the full Onboard Provider reference.

4. Submit your first session

After a therapist completes an appointment, submit the session. Just send the diagnosis codes and session duration — no clinical note or CPT codes required:

curl -X POST https://api.usetaiga.com/api/v1/partner/sessions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "providerNpi": "1234567890",
    "patient": {
      "firstName": "Sarah",
      "lastName": "Johnson",
      "dateOfBirth": "1988-05-15",
      "gender": "F",
      "address": {
        "street": "2222 Random St",
        "city": "New York",
        "state": "NY",
        "zip": "10001"
      },
      "insurance": {
        "memberId": "MEM-2026-0042",
        "payerName": "Cigna"
      }
    },
    "session": {
      "dateOfService": "2026-04-01",
      "placeOfService": "telehealth",
      "durationMinutes": 45,
      "diagnosisCodes": [
        { "code": "F32.1", "description": "Major depressive disorder, single episode, moderate" }
      ]
    }
  }'

We derive the CPT code from the session duration (45 min → 90834). You'll get back a sessionId and status: "processing". You can also send explicit CPT codes or a clinical note — see the full Submit Session reference for all options.

Before submission, you can autocomplete the insurance carrier with Search Payers. Use the returned carrier name for patient.insurance.payerName, and send patient.insurance.payerId too when you have it.

5. Monitor billing status

Via the API

Poll the detail endpoint:

curl https://api.usetaiga.com/api/v1/partner/sessions/SESSION_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

Or list sessions for your organization:

curl "https://api.usetaiga.com/api/v1/partner/sessions?limit=25" \
  -H "Authorization: Bearer YOUR_API_KEY"

Status values: processing → submitted → accepted → paid

See List Sessions, Session Status, and Polling for recommended intervals.

What happens after you submit

Here's what Taiga does with each session:

1. Validate — We verify all required fields and check the provider is onboarded.
2. Code — If you sent a clinical note, our AI extracts ICD-10 and CPT codes. If you sent codes directly, we use them as-is.
3. Review — A physician reviews and approves the codes.
4. Scrub — We validate the claim against payer-specific rules before submission.
5. Submit — The 837P claim is submitted to the insurance payer.
6. Track — We process acknowledgments and remittance responses and update the status.

You can monitor all of this through the session list and detail APIs.

Next steps