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

# Test mode

> How to test an integration today, and what still touches real systems

> [!WARNING]
>
> HealOS has **no sandbox or test-mode keys yet**. Every key works against
> production, and every call has real effects in the organization the key
> belongs to.

## Test in a separate organization

Until a sandbox exists, build and test against a **separate HealOS
organization** that holds only fake data:

1. Create a second organization in the HealOS dashboard, for example
   "Acme Clinic (Test)". Ask your HealOS contact if you need help.
2. Create API keys **in that organization** (Account Settings → API Keys).
   A key only ever sees the organization it was created in, so a test key can't
   read or change your real patients.
3. Call [`GET /me`](https://docs.healos.ai/api-reference/account/describe-the-calling-api-key) first
   in every script and check that `data.org.name` is the test organization.
4. Use clearly fake data: names like "Testy Quickstart", a date of birth of
   `1970-01-01`, phone numbers in the fictional `555-01xx` range and
   `external_id` values starting with `test-`.

## What still has real effects in a test organization

| Action | Real effect | How to limit it |
| - | - | - |
| Create, update or delete patients, documents, appointments | Changes the test organization only | None needed |
| [Generate a note](https://docs.healos.ai/clinical-notes.md#generate-a-note-from-text) from text or audio | Uses one **Scribe session** from that organization's plan | Generate only the notes you need |
| [Generate](https://docs.healos.ai/clinical-notes.md#generate-a-note-from-documents) or [regenerate](https://docs.healos.ai/clinical-notes.md#regenerate-a-note) a note | Runs AI note generation | Same as above |
| [Run an eligibility check](https://docs.healos.ai/recipes/eligibility-check.md) | Sends a **billable** request to the real payer | See below |
| [Check prior-auth decisions now](https://docs.healos.ai/prior-auth.md#check-decisions-now) | Signs in to Availity as the organization | Only works when the organization has an Availity workflow |
| Webhooks | Sends events to the URL you register | Point test webhooks at a test endpoint |

### Eligibility checks

Payers only answer for real members, so there is no way to run a meaningful
eligibility check on made-up data. A made-up member usually comes back as a
payer error (`422`) or a "not found" issue, and can still be billed. Build and
test the code that handles the response with the
[example response](https://docs.healos.ai/benefits.md#2-run-a-check), then run a small number of real
checks under your business associate agreement.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.