Introduction
Refer patients to licensed physiotherapists across Nigeria, follow every referral to discharge, and earn on the care you send — through one REST API, no-code referral links and signed webhooks.
Rehabify Health connects patients with MRTBN-licensed physiotherapists across Nigeria, for in-person and virtual care. Joy, our WhatsApp care assistant, works alongside our care team to handle patient intake and scheduling.
The Rehabify Partner Platform lets HMOs, hospitals and clinics, employers, gyms and digital health products send patients to Rehabify, follow each referral's progress, and reconcile commissions on the care they generate.
Three ways to integrate
You can use any combination of these options.
| Option | What you do | Best for |
|---|---|---|
| REST API | Create referrals from your own system and read their status, sessions and progress reports. | HMOs, EHRs, telemedicine and health apps |
| No-code referral links | Share a co-branded link or QR code. Patients refer themselves through a short form on physioaroundme.com. | Clinics, employers, gyms and campaigns that have no engineering capacity |
| Webhooks | Get a signed, real-time event every time a referral changes status. | Anyone who needs to keep their own records in sync automatically |
The referral journey
Every referral moves through the same public statuses, whether you created it through the API, a referral link or the Partner Portal:
received: Rehabify accepted the referral.contacted: our care team or Joy reached the patient and intake has started.booked: a physiotherapist was matched and the first appointment is confirmed.in_treatment: rehabilitation sessions are under way.completed: the care episode is complete and the patient has been discharged.
A referral can also end as not_suitable (Rehabify isn't the right service and the patient was redirected to appropriate care), cancelled, or closed (no further activity expected). The referral object lists every status.
Environments
Sandbox and live share one base URL. The API key you send decides which environment you're working in.
| Sandbox | Live | |
|---|---|---|
| Key prefix | sk_test_ | sk_live_ |
| Base URL | https://api.physioaroundme.com/v1 | https://api.physioaroundme.com/v1 |
| Patients | Test data only. Nobody is contacted, and no emails or WhatsApp messages are sent. | Real patients are contacted by Rehabify's care team and Joy. |
| Providers | Simulated | Verified physiotherapists |
| Commissions | Never earned | Earned on verified paid bookings |
| Available | Once Rehabify approves your organisation | Once Rehabify approves your production access |
See Authentication for keys and the go-live process, and Sandbox & testing for magic phone numbers and test endpoints.
Your data and your patients' data
- Clinical notes you send to Rehabify are shared with Rehabify clinicians only. The API and webhooks never return them.
- Webhooks never contain patient personal data. To get the patient details you submitted, call the API.
- Progress reports contain no clinical notes. They show session counts and milestones only.
- The public tracking page at
https://physioaroundme.com/track/<tracking_code>shows only the status timeline, with no personal or clinical data.
Start here
Quickstart
Create a sandbox referral, read it back and receive a signed webhook in about 15 minutes.
Authentication
API keys, environments, key rotation, and how to get production access.
API reference
Every endpoint, with request and response examples and an OpenAPI spec.
No-code referral links
Send patients to Rehabify without writing any code.
Key URLs
| What | URL |
|---|---|
| API base URL | https://api.physioaroundme.com/v1 |
| Partner Portal (keys, webhooks, referral links, go-live) | https://partners.physioaroundme.com |
| Documentation | https://docs.physioaroundme.com |
| OpenAPI spec | https://physioaroundme.com/openapi.json |
| Patient site | https://physioaroundme.com |
| Joy on WhatsApp | +234 806 152 5811 (https://wa.me/2348061525811) |
Need help?
Email partners@physioaroundme.com. If your question is about a specific API call, include the X-Request-Id response header (for example, req_5f2c9a1b7d3e4f60a1b2c3d4). It helps us find the request quickly.