PACE Partner API
Environments and data access
Sandbox and live, one organisation per client, privacy rules.
Sandbox and live
There is one base URL, https://mypacehub.com. What a client sees depends on the organisation it belongs to.
| Environment | Who gets it | Data |
|---|---|---|
sandbox | Clients of a simulation organisation | Realistic demo data, rebuilt nightly. No real patients, ever. |
live | Clients of a live organisation | Your organisation's real programme data, within your scopes. |
GET /api/v1/me/ tells you which one your credentials belong to. Build and test against a sandbox client first, then ask PACE for a live client. Sandbox and live clients have different credentials, so a test system cannot reach live data by mistake.
One organisation per client
A client belongs to exactly one organisation and only ever sees that organisation's data. There is no client that can read across organisations.
Privacy rules
These follow the same rules the PACE application applies on screen.
- Pharma clients receive de-identified programme data only. No names, phone numbers, hospital record numbers or patient level records.
- Patient level data goes only to the treating hospital, and only for patients who have consented.
- The patient's consent is recorded by PACE. A referral from a hospital system still asks the patient for consent over WhatsApp before any message is sent.
Audit trail
Every request to /api/v1/ is recorded against your client: method, path, status, time, duration and source address. Request bodies and query strings are never stored. Do not put patient information in a URL.