Convert lead to client
Promotes a lead to an Active client by setting the underlying entity’s client status from Lead to Active.
The same entityKey continues to identify the record; after conversion it appears in GET /api/v1/entities/list rather than lead list endpoints.
Requires an API client with write access. Integration sync to connected practice-management systems runs in the background after conversion (same as updating a client in the app).
400: Entity is already a client (not lead status).
404: Lead not found for your practice.
403: API client is read-only.
429: Rate limit exceeded.
Authorizations
Swagger / Postman only: Client ID as username, Client secret as password. In Postman, set this once on the collection (Authorization → Basic Auth) so all requests inherit. For production server-to-server code, prefer X-OM-Auth-ID and X-OM-Auth-Key headers.
Path Parameters
Lead entity key (identifier).