How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Medblocks Platform API

Server-to-server developer API for the Medblocks Platform. Create patients, start hosted PatientSessions that authorize a patient against one or more EHRs, inspect the resulting connections, read unified FHIR records with cursor pagination, and register/rotate/inspect webhook endpoints and deliveries. Bearer-authenticated with a workspace API key (mb_sk_live_ / mb_sk_sbx_), date-pinned via an optional Version header, and every non-2xx response carries a typed error envelope.

This API exposes 22 operations across 16 paths, and defines 17 schemas. It is described by OpenAPI 3.1.1, at version 2026-04-25.

Requests are made against a single base URL, https://app.medblocks.com.

22 operations 16 paths 17 schemas 3 DELETE12 GET1 PATCH5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.1
API Version
2026-04-25
Base URL
https://app.medblocks.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Medblocks Platform API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API key (mb_sk_live_...)) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Medblocks API key for server-side requests.

Paths & Operations 22

Across 16 paths, the API surfaces 22 operations — 3 DELETE, 12 GET, 1 PATCH, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Operations 22
GET
/health
Liveness check
api.health → 200
POST
/patients
Create a patient
api.createPatient 1 param body → 200400401403404409429500
GET
/patients
List patients
api.listPatients 5 params → 200400401403404409429500
GET
/patients/{id}
Retrieve a patient
api.getPatient 2 params → 200400401403404409429500
PUT
/patients/{id}
Update a patient
api.updatePatient 2 params body → 200400401403404409429500
DELETE
/patients/{id}
Delete a patient
api.deletePatient 2 params → 200400401403404409429500
DELETE
/patients/{id}/connections/{connection_id}
Disconnect a connection
api.disconnectPatientConnection 3 params → 200400401403404409429500
GET
/patients/{id}/patient-sessions
List patient sessions for a patient
api.listPatientSessionsForPatient 5 params → 200400401403404409429500
GET
/patients/{id}/records
Get patient records
api.getPatientRecords 7 params → 200400401403404409429500
GET
/connections/{id}
Retrieve a FHIR source
api.getFhirSource 2 params → 200400401403404409429500
GET
/connections
List FHIR sources
api.listFhirSources 5 params → 200400401403404409429500
POST
/patient-sessions
Start a patient session
api.initPatientSession 1 param body → 200400401403404409429500
GET
/patient-sessions/{id}
Retrieve a patient session
api.retrievePatientSession 2 params → 200400401403404409429500
GET
/launch-contexts/{id}
Retrieve an EHR launch context
api.retrieveLaunchContext 2 params → 200400401403404409429500
POST
/webhooks
Register a webhook endpoint
api.createWebhook 1 param body → 200400401403404409429500
GET
/webhooks
List webhook endpoints
api.listWebhooks 4 params → 200400401403404409429500
GET
/webhooks/{id}
Retrieve a webhook endpoint
api.getWebhook 2 params → 200400401403404409429500
PATCH
/webhooks/{id}
Update a webhook endpoint
api.updateWebhook 2 params body → 200400401403404409429500
DELETE
/webhooks/{id}
Delete a webhook endpoint
api.deleteWebhook 2 params → 200400401403404409429500
POST
/webhooks/{id}/rotate-secret
Rotate the signing secret for a webhook endpoint
api.rotateWebhookSecret 2 params → 200400401403404409429500
GET
/webhooks/{id}/events
List recent webhook events for an endpoint
api.listWebhookEvents 5 params → 200400401403404409429500
POST
/events/{id}/redeliver
Manually redeliver a webhook event
api.redeliverWebhookEvent 2 params → 200400401403404409429500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PatientSession (13 properties), WebhookEvent (13 properties), WebhookEndpointWithSecret (11 properties), WebhookEndpoint (10 properties). Each schema is shown below with its type and property counts.

PatientSession
object
13 properties 13 required
Patient
object
6 properties 6 required
PatientDetail
object
7 properties 7 required
PatientDeleted
object
3 properties 3 required
ConnectionDisconnected
object
3 properties 3 required
PatientRecords
object
6 properties 6 required
FhirSource
object
7 properties 7 required
WebhookEndpoint
object
10 properties 10 required
WebhookEndpointWithSecret
object
11 properties 11 required
WebhookEndpointDeleted
object
3 properties 3 required
WebhookEvent
object
13 properties 13 required
PatientSessionInitInput
object
9 properties 2 required
PatientCreateInput
object
4 properties 1 required
PatientReplaceInput
object
4 properties 1 required
WebhookEndpointCreateInput
object
4 properties 2 required
WebhookEndpointUpdateInput
object
5 properties
ErrorEnvelope
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medblocks-platform-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of Medblocks Platform API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.