Follow-up policy
What counts as a follow-up rather than a new visit, at one location.
GET /v1/addresses/{addressId}/follow-up-policysystemType is SCHEDULED or QMS — the two booking systems have separate
follow-up rules.
API-key only (a widget session is refused) and entitlement-gated on devapi_catalog_booking_policy.
Path parameters
| Name | Required | Description |
|---|---|---|
addressId | Yes | — |
Query parameters
| Name | Required | Description |
|---|---|---|
systemType | No | Which booking system the policy is for. |
Try it
/v1/addresses/:addressId/follow-up-policyAPI key onlydevapi_catalog_booking_policyPath
Query
GET /v1/addresses//follow-up-policyhttps://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/addresses/1/follow-up-policy" \
-H "x-api-key: $MEDOS_API_KEY"Common failures
| Status | Cause |
|---|---|
403 with requiredFeature | Not entitled to this operation. |
403 "only available to Developer API keys" | A widget session token was used. Send x-api-key. |