Skip to main content
Hi Doctor offers two patient-authorised integrations, the MCP connector and the patient REST API, plus a Partner API for platforms with a partner agreement. The MCP connector suits an AI assistant acting for one patient in a conversation, and the REST API suits your own app calling from its server. A credential for one surface never works on another. Last reviewed: 2026-11-04

​
Should you use the MCP connector or the REST API?

MCP tokens are rejected by the REST API, and REST tokens are rejected by the MCP endpoint. A chat product that already holds a patient’s REST session can also run the questionnaire over plain HTTP; see HTTP chat integration.

​
When should you use the Partner API?

Use the Partner API when your platform collects the medical questionnaire in its own product and submits each consultation for its users. It uses server-side API keys, a test mode that never reaches a doctor, and signed webhooks for every status change. Access to the Partner API is granted per partner agreement; the commercial side is on Partner with Hi Doctor.

​
What can a patient integration do?

For a patient account, the documented tasks are:
  • completing a health questionnaire and submitting it for a doctor to review
  • creating a Stripe checkout link for the consultation
  • reading consultations, prescriptions and payments
  • reading and sending messages to the medical team
  • keeping the progress journal
  • checking, cancelling or reactivating a plan
The exact tools are in the patient tools reference, and the exact endpoints are in the API reference. Not every website feature is available on both surfaces.

​
Which steps need a person?

​
Is the brand header a credential?

No. REST requests send X-Brand-Slug: hi-doctor, but the header creates no partner account and grants no access by itself. The patient surfaces offer no service accounts, organisation-wide credentials or access to several patients with one credential. Every patient integration works through the individual patient’s account.

​
Frequently asked questions

​
Can I use an MCP token with the REST API?

No. MCP tokens are rejected by the REST API, and REST tokens are rejected by the MCP endpoint.

​
How long do access tokens last?

An MCP access token lasts up to 1 hour and a REST access token 1 day. Refresh tokens last 30 days on both.

​
Can the MCP connector upload photographs?

Only from an app that supports the connector’s protected upload, which returns a file reference the upload tools accept. Otherwise the patient uploads on the website, or your application uses the REST API.

​
Is the X-Brand-Slug header a credential?

No. It identifies the brand for the documented Hi Doctor flows, but it grants no access by itself.

​
Can one credential access several patients?

Not on the patient surfaces: the MCP connector and the REST API act for one patient at a time. Platforms that submit consultations for many users use the Partner API under a partner agreement.

​
Can I build a chat product on the REST API?

Yes. A chat product that holds a patient’s REST session can run the questionnaire over plain HTTP, as described in the HTTP chat integration guide.

​
Next steps

Data and consent

What flows to your integration and what you must establish.

API quickstart

Sign in and make a first read.

Connect the MCP

Sign-in, consent and disconnecting.

Discuss your integration

Write to hello@hi-doctor.ai.