Add Patient Insurance
Queue the addition of insurance information to a patient record in the EMR system via RPA (Robotic Process Automation).
This endpoint queues the addition of insurance information to a patient record in the EMR system. The operation is asynchronous and returns immediately with aDocumentation Index
Fetch the complete documentation index at: https://docs.usecobalt.com/llms.txt
Use this file to discover all available pages before exploring further.
job_id for tracking. Results are delivered via webhook.
eClinicalWorks, plan_begin_date is required. If relationship_to_subscriber is a non-self value such as spouse, child, or other, subscriber_demographics.first_name and subscriber_demographics.last_name are also required.emr_insurance_id. In eClinicalWorks, this is the same record identifier returned later as emr_insurance_id in POST /v1/patients/fetch with include: ["insurances"], and it can be used with the insurance update endpoint.Insurance Provider Resolution
The API supports three methods for identifying the insurance provider (in order of priority):-
By Cobalt Provider ID (Most specific, recommended):
-
By Name + Payer ID (Most specific when ID not available):
-
By Name Only (Least specific, may match first result if multiple exist):
GET /v1/insurance-providers to retrieve the correct insurance provider identifiers for your organization.Validation Rules
Address Validation
- State: Must be a valid two-letter US state abbreviation (accepts lowercase, e.g., “ca” or “CA”)
- ZIP Code: Must be either 5 digits (e.g., “90001”) or 9 digits with hyphen (e.g., “90001-1234”)
Date Validation
- plan_begin_date: Must be in YYYY-MM-DD format (e.g., “2025-01-15”)
Priority (Optional)
- priority: Insurance priority level (valid values: “1”, “2”, “3”). When not provided, the EMR will use its default priority setting.
Relationship to Subscriber
Accepts both codes and names (case-insensitive):- Codes: “01”, “02”, “32”, “33”, “17”, “20”, “53”, “25”
- Names: “self”, “spouse”, “mother”, “father”, “step parent”, “employee”, “life partner”, “other”
Insurance Provider Validation
insurance_payer_idalone is not supported (must be combined withinsurance_name)- If provider ID, name, or name+payer_id combination is not found, returns 404 with helpful message
Example Requests
Minimal Request (Using Insurance Provider ID)
Complete Request (Using Insurance Name + Payer ID)
Self-Insured Patient with 9-Digit ZIP
Example Response
Webhook Events
After the insurance addition is processed, a webhook event will be sent to your configured webhook URL.Success Event (patient.insurance.added)
eClinicalWorks, emr_insurance_id is the EMR-native insurance record ID. The same value is returned in live fetch as emr_insurance_id and should be used when calling PATCH /v1/patients/:patient_mrn/insurances/:emr_insurance_id.audit_trail is still present for some EMRs, including Experity and EZDERM. It is not currently included in the eClinicalWorks insurance success payload, so the example above reflects the eCW shape.Failure Event (patient.insurance.failed)
patient_insurance_id and job_id, then listen for webhooks to determine the final status.Authorizations
Path Parameters
The Medical Record Number (MRN) of the patient in the EMR system
Body
Insurance member/policy ID
"MEM123456789"
Insurance group number
"GRP98999"
Cobalt insurance provider ID (Priority 1). Use GET /v1/insurance-providers to retrieve valid IDs.
"insurance-provider-123"
Insurance company name (Priority 2)
"Blue Cross Anthem"
Insurance payer ID (Priority 3)
"98999"
Insurance priority level (1=primary, 2=secondary, 3=tertiary)
1, 2, 3 "1"
Insurance coverage start date in YYYY-MM-DD format
^\d{4}-\d{2}-\d{2}$"2026-01-01"
Copayment amount in dollars
x >= 025
Patient's relationship to insurance subscriber
"self"
Insurance subscriber demographics