> ## Documentation Index > Fetch the complete documentation index at: https://docs.teamcaredental.com/llms.txt > Use this file to discover all available pages before exploring further. # List insurance verifications > This endpoint retrieves insurance verifications for a specific location, synced from the PMS. Each patient's plan enrollment and each insurance plan's benefits has one current verification; earlier verifications are included as history rows sharing the same `pms_insurance_verification_id`. Use the `id` of a verification to post a Stedi eligibility result with `PATCH /locations/{location_id}/insurance_verifications/{insurance_verification_id}`. #### Parameters - location_id (required): The ID of the location for which insurance verifications are to be retrieved. - after: A parameter to specify the cursor for pagination. - items: A parameter to specify the number of items to be returned. - The `q[fetch_modified_since]` is used to capture the delta changes, pass the datetime in UTC as shown in example below ```json { "q": { "fetch_modified_since": "2026-10-01T00:00:00.000Z" } } ``` ## OpenAPI ````yaml https://app.teamcaredental.com/openapi-vendors.json get /locations/{location_id}/insurance_verifications openapi: 3.1.0 info: title: TeamCare Vendor API version: 1.0.0 description: >- > ⚠️ **Deprecation notice:** Support for the v1 Vendor API ends on **November 7, 2026** (end of the first week of November). Please migrate to **v2**, which moves to `https://api.teamcaredental.com/api/v2/vendors` and replaces the per-request `location_id` in the URL with a slot-based model: request a location's slot once, then pull all of its data using the `X-Vendor-Request-Key` header. See the [changelog](https://docs.teamcaredental.com/changelog) for the full migration guide. Vendor APIs for integrating dental office data. HIPAA-compliant and opt-in. servers: - url: https://app.teamcaredental.com/api/v1/vendors security: - bearerAuth: [] paths: /locations/{location_id}/insurance_verifications: get: tags: - Insurance Verifications summary: List insurance verifications description: >- This endpoint retrieves insurance verifications for a specific location, synced from the PMS. Each patient's plan enrollment and each insurance plan's benefits has one current verification; earlier verifications are included as history rows sharing the same `pms_insurance_verification_id`. Use the `id` of a verification to post a Stedi eligibility result with `PATCH /locations/{location_id}/insurance_verifications/{insurance_verification_id}`. #### Parameters - location_id (required): The ID of the location for which insurance verifications are to be retrieved. - after: A parameter to specify the cursor for pagination. - items: A parameter to specify the number of items to be returned. - The `q[fetch_modified_since]` is used to capture the delta changes, pass the datetime in UTC as shown in example below ```json { "q": { "fetch_modified_since": "2026-10-01T00:00:00.000Z" } } ``` operationId: locations_resources_insurance_verifications_list parameters: - name: location_id in: path required: true description: >- The ID of the location for which insurance verifications are to be retrieved. schema: type: string example: '58' - name: after in: query required: false description: A parameter to specify the cursor for pagination. schema: type: integer example: 241094833 - name: items in: query required: false description: A parameter to specify the number of items to be returned. schema: type: integer example: 500 - name: q in: query required: false style: deepObject explode: true schema: type: object properties: fetch_modified_since: type: string format: date-time example: '2026-10-01T00:00:00.000Z' example: fetch_modified_since: '2026-10-01T00:00:00.000Z' responses: '200': description: Successful response content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string type: type: string example: insurance_verification attributes: type: object properties: deleted: type: boolean insurance_plan_id: type: - number - 'null' description: >- Insurance plan verified. Set for `insurance_benefit` verifications. patient_insurance_plan_id: type: - number - 'null' description: >- The patient's insurance plan (Open Dental `patplan`) verified. Set for `patient_enrollment` verifications. pms_insurance_verification_id: type: - string - 'null' description: >- The PMS verification ID (Open Dental `InsVerifyNum`). History rows share the ID of the current verification they belong to. verify_type: type: string enum: - patient_enrollment - insurance_benefit description: >- `patient_enrollment` verifies a patient's coverage; `insurance_benefit` verifies a plan's benefits. verified_date: type: - string - 'null' format: date-time description: When the coverage was last verified. status: type: - string - 'null' description: >- Verification status name as configured in the PMS, e.g. `Verified`, `Unverified`. note: type: - string - 'null' updated_at: type: string format: date-time pagy: type: object properties: has_more: type: boolean items: type: integer example: data: - id: '5512' type: insurance_verification attributes: deleted: false insurance_plan_id: null patient_insurance_plan_id: 8841 pms_insurance_verification_id: '412' verify_type: patient_enrollment verified_date: '2026-10-01T14:03:11.000Z' status: Verified note: >- Active Coverage. Humana Gold Plan. Member ID HUMANA123. Group 11223344. Plan 2024-01-01 to open. Verified through Stedi ec_01a06d4a-a0fa-77d2-8b49-ca9a74c9888a updated_at: '2026-10-01T14:03:11.000Z' pagy: has_more: true items: 1 '401': description: Missing, invalid or expired token. content: application/json: schema: type: object properties: errors: type: string example: errors: not authorized '403': description: The credential may not access this resource. content: application/json: schema: type: object properties: errors: type: string example: errors: access Denied '404': description: Resource not found. content: application/json: schema: type: object properties: errors: type: string example: errors: resource not found '422': description: The request could not be processed. content: application/json: schema: type: object properties: errors: type: string example: errors: ... '429': description: >- Concurrency limit exceeded. The request was not executed; retry is safe. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer content: application/json: schema: type: object properties: errors: type: string sync_type: type: string enum: - initial - incremental max_concurrent_locations: type: integer active_location_ids: type: array items: type: integer retry_after_seconds: type: integer example: errors: >- Too many locations syncing concurrently. At most 5 locations may have initial sync requests in flight at a time. sync_type: initial max_concurrent_locations: 5 active_location_ids: - 101 - 102 - 103 - 104 - 105 retry_after_seconds: 1 components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT returned by POST /auth/token. Valid for six hours. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.