Import or update a legacy patient care plan
Imports or updates a legacy patient care plan for a clinic patient.
If an existing patient care plan for the same PIM patient ID and core Care Plan ID already exists and has a status of IMPORTED, it will be updated instead. Patient care plans with any other status, including imported patient care plans that have already been marked ACTIVE, cannot be updated through this endpoint.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Schema for importing a legacy patient care plan via the external API.
The amount paid for the care plan
x >= 0The care benefits to import for the care plan
The core Care Plan ID to enroll the patient into
The clinic ID for the patient and client being imported
End date for the care plan (YYYY-MM-DD). This is non-inclusive, meaning a plan ending on 2/1/2026 would not be considered active/usable on 2/1/2026.
The enrollment fee of the care plan
x >= 0Whether billing is monthly (True) or upfront (False)
The PIM client ID to import the care plan for
The PIM patient ID to import the care plan for
The cost of the care plan
x >= 0Whether the plan should automatically renew at the end of term
Start date for the enrollment (YYYY-MM-DD)
The status of the care plan. Must be one of: IMPORTED, ACTIVE, TERMINATED
IMPORTED, CLIENT_CREATED, CLINIC_CREATED, ACTIVE, TERMINATED, PAYMENT_FAILED, SUSPENDED Optional Vetcove client ID. When provided, bypasses PIM ID lookup and resolves the client by primary key (scoped to clinic). Use this to disambiguate when multiple clients share the same pim_client_id.
Optional Vetcove patient ID. When provided, bypasses PIM ID lookup and resolves the patient by primary key (scoped to clinic). Use this to disambiguate when multiple patients share the same pim_patient_id.
Optional next core Care Plan ID for automatic renewal
Optional Vetcove payment method ID. When provided, takes precedence over stripe_payment_method_id and resolves the payment method by primary key (scoped to the client). Both payment method fields are optional for all statuses. Omitting both means the payment method must be updated later before billing.
Optional legacy Stripe payment method ID to use for billing. payment_method_id takes precedence when both fields are provided. Both payment method fields are optional for all statuses. Omitting both means the payment method must be updated later before billing.
Response
OK
The ID of the Care Plan this patient-specific plan is linked to
The type of the care plan
CORE, ADD_ON, SERVICE_PACKAGE The name of the care plan this patient care plan is linked to
The ID of the clinic client this patient care plan is associated with
The ID of the clinic this patient care plan is associated with
The ID of the clinic patient this care plan is associated with
The ID of the core patient care plan this one is linked to, if this is an add-on plan
When this care plan was deactivated, if applicable
The name of the user who deactivated the care plan, if applicable
End date for the care plan (YYYY-MM-DD). This is non-inclusive, meaning a plan ending on 2/1/2026 would not be considered active/usable on 2/1/2026.
The enrollment fee of the care plan
x >= 0The unique identifier for the patient care plan
Whether the care plan is billed monthly or upfront
The monthly cost of the care plan, in cents. Only applicable to monthly billed care plans.
x >= 0The date of the next payment for the care plan, if applicable
The ID of the next care plan, if applicable
The ID of the payment method associated with this care plan
The cost of the care plan
x >= 0The remaining balance of the care plan, in cents
Whether this care plan will automatically be renewed
The start date of the care plan
The status of the patient care plan
IMPORTED, CLIENT_CREATED, CLINIC_CREATED, ACTIVE, TERMINATED, PAYMENT_FAILED, SUSPENDED