Public profile bundle
The workspace public profile plus its published practitioner profiles, in one call.
GET /v1/public-profiles/sdkThe same bundle workspace detail nests
under publicProfile, without the workspace payload around it.
Like the list, this does not go through enrich(), so slug, gallery, faqs
and seo come back null.
entitlement-gated on devapi_public_profiles_sdk.
Try it
/v1/public-profiles/sdkdevapi_public_profiles_sdkDeclared before the :profileId route, so the literal is not captured by the param route.
GET /v1/public-profiles/sdkhttps://api.medos.oneUse a dedicated test key, and put your browser's address on its allowlist
A Developer API key authenticates on its own, so it only works from the addresses registered against it — and this page calls from your browser, not your servers. Unless your own public address is on the list you get a 403 naming it, which is the allowlist doing its job. Your browser may also reach us over IPv6 even when your server does not, so the address in the error is often not the one you expected. The key here is kept in memory only and never written to storage, but create a test key for it and deactivate that key when you are done.
Request
curl -s "https://api.medos.one/v1/public-profiles/sdk" \
-H "x-api-key: $MEDOS_API_KEY"Common failures
| Status | Cause |
|---|---|
403 with requiredFeature | Not entitled to this operation. |