Update Service V1

March 2026

POST /api/services/{id} → POST /api/services/v2/{id}

Context

The original endpoint potentially includes a synchronous, blocking call through to insurance payers. For predictable behavior and reliability, these are deprecated in favor an asynchronous pattern.

See the Synchronous API Migration Guide for the broader pattern (polling, streaming, webhooks).

Changes

The v2 endpoint returns the current Service from the database immediately after the update. coverageStatus and nested eligibility may still reflect an in-flight refresh until the workflow finishes.

Migration

Point clients at POST /api/services/v2/{id} with the same request body shape as v1 update (patientToken and patch fields as documented on that endpoint).

Priority

For most partners, this is an important part of their user experience, and asynchronous APIs will perform better.