# Getting started with the Eirly Health staging environment

Staging is a full copy of the platform for trying things out: the same app and API, separate accounts, a test card instead of a real one. Nothing you order in staging reaches a lab. Pick your path and follow the steps.

- Cost: Free
- Reaches a lab: Never
- Accounts: Separate from production
- Keys: Staging only

## I want to try the platform

Practitioners, operations, founders: no code.

### Step 1: Create an account

Where: app.staging.eirly.health/signup (https://app.staging.eirly.health/signup)

Sign up with an email and password, or with Google. Use an email you can read: the test referral in step 6 is sent to the address you give.

You will know it worked when: You are signed in and the app asks you to complete your profile.

### Step 2: Verify your profile

Where: Profile, on first sign-in

Finish the profile and select a practitioner type. Choose Other if none fits. The organisation step stays locked until the profile is verified.

You will know it worked when: The app offers to create an organisation.

### Step 3: Create an organisation

Where: Create organisation

The organisation owns your referrals, results, members and billing. Name it after your service. One organisation per service is the usual shape.

You will know it worked when: You land on the organisation's dashboard.

### Step 4: Add the test card

Where: Settings, then Billing

Stripe's test card: any future expiry, any CVC. Staging never charges a real card. A card on file is needed before commercial ordering and before API access can be enabled.

Test card number: 4242 4242 4242 4242

You will know it worked when: Billing shows a card ending 4242.

### Step 5: Build a bundle

Where: Bundles, then New bundle

Pick a few tests. The billing toggle shows Commercially billed (every test, with prices). The Medicare option (eligible tests, no prices) appears only once a provider number and signature are on file, which you can skip for a first try.

You will know it worked when: The bundle is saved and appears in your list.

### Step 6: Order for a made-up client

Where: The bundle, then Buy for

Invent the client's details. Never use a real person in staging. The referral is issued and emailed to the address you give, with a sign-up link for the client.

You will know it worked when: The referral appears under Referrals, and the email arrives.

### Step 7: Look around

Where: Referrals, Results, Clients

Open the referral, download its PDF, and see what your team would see day to day. Results in staging arrive as test data where the environment provides them.

You will know it worked when: You can find the referral and its PDF.

### Step 8: Invite a colleague

Where: Members, then Invite

Choose a role: Owner, Admin, Support, Read-only, or a custom role. Roles add up. Medicare ordering is opt-in and needs its own role with the capability Order with Medicare provider number.

You will know it worked when: The invitation shows as pending until they accept.

## I want API keys

Developers and healthtechs building an integration. Follow the steps below, or go straight to the docs.

### Step 1: Create an account, verify, create an organisation

Where: app.staging.eirly.health/signup (https://app.staging.eirly.health/signup)

Steps 1 to 3 of the no-code path. A verified profile (pick a practitioner type, Other if unsure) is required before an organisation can exist, and all API access is scoped to an organisation.

You will know it worked when: You are on the organisation's dashboard.

### Step 2: Add the test card

Where: Settings, then Billing

A billing method must be on file before API access can be enabled. Staging accepts Stripe's test card and never charges it.

Test card number: 4242 4242 4242 4242

You will know it worked when: Billing shows a card ending 4242.

### Step 3: Enable the API

Where: Settings, then API Keys

Follow the steps to enable API access. You receive a client_id and a client_secret for staging. Keep the secret on your server and in your CI's secrets; it never goes in a browser or a repository.

You will know it worked when: A client_id and client_secret are shown once; you have stored them.

### Step 4: Get a token

Where: Your terminal

Exchange the credentials for an access token with the client credentials flow. The token lasts an hour; a refresh token comes with it.

```
curl -X POST https://auth.staging.eirly.health/oauth/token \
  -u "$CLIENT_ID:$CLIENT_SECRET" \
  -d grant_type=client_credentials
```

You will know it worked when: The response carries access_token and expires_in 3600.

### Step 5: Make the first call

Where: Your terminal

List the tests, then find the five centres nearest Sydney. Every list endpoint pages the same way, with a cursor.

```
curl https://api.staging.eirly.health/v1/tests -H "Authorization: Bearer $TOKEN"
curl "https://api.staging.eirly.health/v1/collection-centres?lat=-33.8688&lng=151.2093&count=5" -H "Authorization: Bearer $TOKEN"
```

You will know it worked when: JSON comes back; the centres carry distanceKm.

### Step 6: Connect the MCP

Where: Claude Code, Cursor, Windsurf, Codex, or any assistant that speaks MCP

The developer MCP is public and read-only: the API reference, schemas, docs and webhook events, read by your coding assistant while it writes your integration. Any tool that speaks MCP over HTTP can connect; the command below is Claude Code's, the others take the same address in their MCP settings.

```
claude mcp add --transport http eirly-dev https://mcp.eirly.health/dev/v1
```

You will know it worked when: Your assistant can list the endpoints tagged Collection centres.

### Step 7: Go to production

Where: app.eirly.health (https://app.eirly.health/signup)

Repeat the setup in production: new account, organisation, billing and keys. Keys from staging do not work there. Production needs a plan, quoted to your volume.

You will know it worked when: Production credentials in your server's secrets; staging ones kept for testing.

## Questions

**Does staging cost anything?** No. The test card is never charged, and API access in staging is free. Production needs a plan.

**Can I use real patient details in staging?** No. Use made-up people. Staging is a test environment and nothing in it goes to a lab.

**Do staging keys work in production?** No. Each environment issues its own client_id and client_secret.

**I am stuck at verification.** Select a practitioner type (Other if unsure) and complete the profile; the organisation step unlocks after that. If it still does not, contact support@eirly.health with the email you signed up with.

**Where are the full developer docs?** docs.eirly.health: Getting Started, Authentication, Workflow, REST API, Webhooks and Medicare Ordering.

## Next

- [Build on the pathology API](https://eirly.health/how-to/build-on-the-pathology-api): Credentials, first request, first referral, webhooks, production.
- [Build a collection centre finder with the Eirly MCP](https://eirly.health/how-to/build-a-collection-centre-finder-with-the-mcp): The first thing to build in staging, prompts included.
- [Set up a telehealth service](https://eirly.health/how-to/telehealth-pathology): Account, organisation, roles, Medicare, ordering, results.

Source: https://eirly.health/how-to/getting-started-with-staging (this file: https://eirly.health/how-to/getting-started-with-staging.md). Eirly Health, Australia. Staging never reaches a lab; use made-up people only.
