---
title: "Create Benefits Check"
method: POST
path: "/public/v1/benefits-checks/"
tags: ["V1BenefitsCheckResource"]
---

# Create Benefits Check

`POST /public/v1/benefits-checks/`

## Request

- Base URL: `https://app.silnahealth.com/api`
- URL: `https://app.silnahealth.com/api/public/v1/benefits-checks/`
- Auth: HTTP bearer

## Headers

- `idempotency-key` string

## Request body

- V1BenefitsCheckCreateBody: Benefits Check Create Request Schema
  - `patient_plan_id` string, uuid, required: Patient Plan ID
  - `specialties` PublicSpecialty[], required: List of specialties to create benefits check for
  - `template_id` string, uuid, nullable: Benefits Check Template ID
  - `diagnosis_code_ids` string[], nullable: Diagnosis code IDs to attach to this benefits check. Use GET /diagnosis-codes to look up IDs by code. If not provided, the patient's diagnosis codes are used. If an empty list is sent, the benefits check is not verified against any diagnosis code, even if the patient has diagnosis codes on record. Diagnosis codes are only attached when benefits check diagnosis codes are enabled for the provider. When they are, a benefits check with different diagnosis codes is not treated as a duplicate of an existing benefits check for the same patient plan and specialty.
  - `network_status_override` 'IN_NETWORK' | 'OUT_OF_NETWORK'
  - `procedure_group_ids` string[], nullable: Procedure group IDs defining the CPT codes this benefits check is verified against. Each procedure group must be configured for one of the requested specialties, and the benefits check template used for this request must allow procedure group selection. Use GET /procedure-groups to look up IDs, optionally by exact CPT codes. A benefits check with different procedure groups is not treated as a duplicate of an existing benefits check for the same patient plan and specialty.
  - `clinician_id` string, uuid, nullable: Clinician to verify benefits as. If provided, this clinician's NPI is used for eligibility requests and payor calls and portals instead of the contracted group. Cannot be combined with provider_group_id. Must be enabled for the provider. Use GET /clinicians to look up IDs.
  - `provider_group_id` string, uuid, nullable: Provider group to verify benefits as. If provided, this group's NPI and TIN are used for eligibility requests and payor calls and portals instead of the contracted group. Cannot be combined with clinician_id. Must be enabled for the provider. Use GET /provider-groups to look up IDs.

## Response `201`

Benefits Check Create Response Schema

- V1BenefitsCheckCreateResponse: Benefits Check Create Response Schema
  - `benefits_check_ids` string[], required: List of created benefits check IDs

## Other responses

- `400`
- `401`
- `429`

## Changes

- **2026-10-13** `0d61bbfc3866`: 2 info
  - added the new optional request property `clinician_id`
  - added the new optional request property `provider_group_id`
- **2026-10-08** `2487b06b9480`: 1 info
  - added the new `NEUROLOGY` enum value to the request property `specialties/items/`
- **2026-09-16** `b09308751f7b`: 1 info
  - added the new optional request property `procedure_group_ids`
- **2026-09-03** `fd526e716e77`: 29 info
  - added the new optional request property `diagnosis_code_ids`
  - added the new optional request property `network_status_override`
  - added the new optional request property `template_id`
  - added the new `ADVANCED_PRIMARY_CARE_MODELS` enum value to the request property `specialties/items/`
  - …25 more

[Operation history](https://skmtc.dev/silnahealth/apis/silna-public-api/changes/public/v1/benefits-checks/post.md)

---

[API](https://skmtc.dev/silnahealth/apis/silna-public-api.md) - [All operations](https://skmtc.dev/silnahealth/apis/silna-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/silnahealth/apis/silna-public-api/revisions/06b4547aa602?raw)