Intake — the thread starts.
The moment a patient completes intake, your systems hear about it — ready to pick up the thread without polling.
Telehealth API & webhooks
Most telehealth APIs exist to fill gaps. We don’t leave any.
Remedora runs intake, the doctor network, e-prescribing, pharmacy, payments, and support as one platform — so there is nothing to stitch together through an API. When your own systems need to react, Remedora sends webhooks: signed, real-time event notifications you can trust.
i. What you can subscribe to
A webhook for every moment that matters.
i.
ii.
Clinical — the decision lands.
When a provider approves, declines, or asks for more information, the outcome is pushed to you the instant it happens.
iii.
Pharmacy — the order moves.
Prescription sent, then shipped, delivered, or flagged as an exception. Every status change in the fulfillment journey, delivered as it happens.
iv.
Billing — the money events.
A charge captured, a subscription renewed or canceled, a payment failed. Revenue events in real time, no nightly reconciliation job.
ii. How delivery works
Events you can actually trust.
i.
Signed — verify before you act.
Every payload is signed. Your endpoint confirms it came from Remedora before doing anything with it — no forged or tampered events.
ii.
Retried — nothing dropped.
If your endpoint is briefly down, Remedora retries automatically. You react to events instead of rebuilding state from nightly exports.
iii.
No-code — point and go.
Configure a webhook at any URL from the dashboard. No API keys to issue or rotate, no engineering ticket to open.
iii. Looking for a REST API?
No REST API. By design.
Teams usually reach for a telehealth API to build the parts their platform is missing — intake from one vendor, prescribing from another, a pharmacy integration after that. Remedora already runs all of it, in one system, under one BAA.
So there is nothing to assemble, and no sprawling API surface to learn, secure, version, and maintain. You get the single integration that actually matters: webhooks that tell your own systems what happened, the moment it happens.
iv. Webhook FAQ
Webhook questions, answered.
Does Remedora have a REST API?
No — and that is deliberate. Remedora is the all-in-one platform: patient intake, the doctor network, e-prescribing, pharmacy fulfillment, payments, and support are already built in and running. There is nothing to assemble through an API, so there is no sprawling API surface to learn, secure, and maintain. The one integration you actually need is to let your own systems react to what happens — and that is what webhooks are for.
What events can I receive webhooks for?
The moments that matter across the patient lifecycle: when a patient completes intake, when a provider approves or declines (or asks for more information), when a prescription is sent and as the shipment moves through shipped, delivered, or exception, and on billing events like a captured charge, a renewed or canceled subscription, or a failed payment.
How do I know a webhook actually came from Remedora?
Every webhook is signed. Your endpoint verifies the signature before acting on the payload, so you never process a forged or tampered event.
What happens if my endpoint is down when an event fires?
Deliveries are retried automatically. A brief outage on your side does not mean lost events — Remedora keeps attempting delivery instead of dropping the notification.
Do I need engineering to set up webhooks?
No. Webhook endpoints are configured from the dashboard — point one at any URL you control. There are no API keys to issue or rotate.
Is webhook data HIPAA compliant?
Yes. Webhook traffic is encrypted in transit, payloads carry only what the event needs, and Remedora signs a BAA as part of onboarding.
vi. Begin
Build on the events, not the plumbing.
All-in-one means there is nothing to integrate. Webhooks mean your systems still never miss a beat.