Deprecated

0.19.7 Member endpoints are deprecated

The legacy Members endpoints are deprecated and scheduled for removal. They still work today, but please migrate — each endpoint's reference page now shows a deprecation notice with its replacement.

What to use instead

DeprecatedReplacement
POST /members (Adding a new member)Create application bundle — submits a member and their dependants in one atomic call, supports externalId
POST /members/cancel (Cancel member)Cancel contract bundle for a planholder and all dependants, or Cancel a single contract holder for one dependant
GET /members (Get multiple members' details)List contract bundles for live coverage state, or List application bundles for submitted applications
GET /members/{memberId} (Get a single member's details)Get application bundle, or List contract bundles for live coverage

Why

Application and contract bundles model a household (planholder + dependants) as one unit: submission is atomic, live policy state (contracts, coverage, costs) is readable in one place, and your own identifiers travel along via externalId. The member endpoints predate this model and can't represent it fully.

No removal date is set yet — it will be announced here with ample notice. The related member.status.changed webhook topic is also deprecated in favor of contract_holder.policy_issued.