Sandbox

Build against a real, synthetic tenant

The sandbox is a live copy of the integration API pointed at a seeded, non-PHI tenant. Get an issued sandbox key, call real endpoints from the console below, and reset the data whenever you need a clean slate.

A seeded tenant

A dedicated sandbox org and facility pre-loaded with synthetic, non-PHI residents, coverage, and clinical data — so you can build against realistic shapes without touching production.

Your own sandbox key

On approval you're issued a client_id + one-time client_secret scoped to the sandbox tenant with read scopes. Same OAuth2 flow as production — just a different tenant.

Resettable data

Sandbox data is periodically reset to a known baseline, and you can request an on-demand reset. Your key survives resets; only the synthetic data returns to baseline.

Sandbox coordinates

Every issued sandbox key is scoped to this tenant. The org and facility ids are stable and safe to hard-code in your sandbox config (they are not secrets).

Base URL	`https://medflo-pcc-vendor-api-eez5kqwsxa-uw.a.run.app`
Token endpoint	`/api/v1/oauth/token`
Sandbox org_id	`sandbox-org-0001`example placeholder — the real seeded id is injected at deploy
Sandbox org code	`SANDBOX`example placeholder
Sandbox facility_id	`sandbox-fac-0001`example placeholder
Default scopes	`residents.read coverage.read clinical.read`

Getting a key

1. Register an app and request read scopes.
2. An admin approves it and issues your sandbox key.
3. Store the one-time client_secret, then unlock the console below.

Try it against the sandbox

Unlock the console with your issued sandbox key, pick a resource, and run the real request. The secret stays in your browser and is only sent to the token endpoint.

Sandbox console

Key required

Runs the real two-step flow against the live sandbox using your issued sandbox key. Nothing is pre-filled; your secret is sent only to the token endpoint and never persisted.

Base URL

https://medflo-pcc-vendor-api-eez5kqwsxa-uw.a.run.app

Sandbox org_id· example id

sandbox-org-0001

Sandbox facility_id· example id

sandbox-fac-0001

A sandbox key is required

Sandbox credentials are issued only after your app is approved. If you have an issued sandbox client_id and client_secret, unlock the console to use them. Otherwise, register an app first.

client_idclient_secret

ResourcescopeResource path (editable)https://medflo-pcc-vendor-api-eez5kqwsxa-uw.a.run.app/api/v1/ofctx/sandbox-org-0001/sandbox-fac-0001/residents?page_size=5

Reset the sandbox

The sandbox tenant is restored to its seeded baseline on a regular schedule. To restore it on demand — for example after a test run that mutated ingest-style data — issue a reset. It only ever affects the synthetic sandbox tenant; production data is never touched.

Sandbox-only, non-destructive to you

A reset restores the seeded synthetic dataset. It does not revoke your key or change your scopes — only the data returns to baseline.

bash

# Request an on-demand sandbox data reset (restores the seeded baseline).
# Requires a sandbox token; only affects the synthetic sandbox tenant — never production.
TOKEN="eyJ..."   # a token from your issued sandbox key

curl -s -X POST \
  'https://medflo-pcc-vendor-api-eez5kqwsxa-uw.a.run.app/api/v1/ofctx/sandbox-org-0001/simulation' \
  -H "Authorization: Bearer $TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{ "action": "reset" }'

Prefer not to script it? Email api-support@medfloai.com and we'll reset your sandbox tenant.