Public profiles
The paged list of published public profiles.
GET /v1/public-profilesUpstream ignores profileType on this route, so the WORKSPACE profile comes back
even when you ask for USER.
entitlement-gated on devapi_public_profiles_list.
Query parameters
| Name | Required | Description |
|---|---|---|
page | No | Zero-based. |
size | No | — |
Try it
/v1/public-profilesdevapi_public_profiles_listUpstream ignores profileType here, so the WORKSPACE profile comes back even when you ask for USER. slug, gallery, faqs and seo are null on this route.
Query
GET /v1/public-profiles?page=0&size=20https://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 -sG "https://api.medos.one/v1/public-profiles" \
-H "x-api-key: $MEDOS_API_KEY" \
--data-urlencode "page=0" \
--data-urlencode "size=20"Only the single read goes through
medos's enrich(), so it is the only source of slug, gallery, faqs and
seo — this list returns those as null.
Common failures
| Status | Cause |
|---|---|
403 with requiredFeature | Not entitled to this operation. |