---
title: "View adjustment (beta)"
method: GET
path: "/adjustments/{id}"
tags: ["Adjustments"]
---

# View adjustment (beta)

`GET /adjustments/{id}`

## Request

- Base URL: `https://nexhealth.info`
- URL: `https://nexhealth.info/adjustments/{id}`
- Auth: API key in header `Authorization`

> 🚧 Beta
>
> Send `Nex-Api-Version: v3.1.0` to use this endpoint. It is still changing, and access is limited to approved partner institutions. Contact NexHealth before you build on it.

> **Changed from v3.0.0:** Adds response fields `data.guarantor.address`, `data.guarantor.address.city`, `data.guarantor.address.line_1`, `data.guarantor.address.line_2` (+35 more); and other schema changes.

This endpoint returns a single ledger adjustment by its NexHealth ID, with optional sideloading of the associated `patient`, `provider`, `guarantor`, `claim`, `charge`, and `adjustment_type`.

## Path parameters

- `id` integer, required

## Query parameters

- `subdomain` string, required
- `include[]` string[]

## Headers

- `Nex-Api-Version` string, required

## Response `200`

Successful

- APIV31EntitiesLedgerAdjustmentWithIncludesResponse: API_V31_Entities_Ledger_AdjustmentWithIncludes_Response model
  - `code` boolean: Indicates the success or failure of the request
  - `description` string: Additional context on the request to help with debugging.
  - `error` string[]: Any errors that occur during the execution of the request.
  - `data` APIV31EntitiesLedgerAdjustmentWithIncludes
    - `id` integer: Resource ID
    - `foreign_id` string: Identifier NexHealth uses to uniquely match this record to its counterpart in the integrated EHR. How it is derived differs between EHRs and may change; treat it as an opaque string and do not parse it.
    - `location_id` integer: The ID of the location that this item is for
    - `patient_id` integer: The ID of the patient that this item is for
    - `guarantor_id` integer: The ID of the guarantor that this item is for
    - `provider_id` integer: The ID of the provider that this item is for
    - `updated_at` string, date-time: Last updated time for item in UTC
    - `description` string: A description of the item
    - `deleted_at` string, date-time: Deleted time for item in UTC
    - `adjustment_amount` APIV2EntitiesPrice
      - `amount` string: The currency value, in whole units (e.g. dollars)
      - `currency` string: The ISO currency code
    - `adjusted_at` string, date: The UTC date adjustment was made
    - `transaction_id` string: The ID of the transaction for this payment
    - `charge_id` integer: The ID of the charge for this payment
    - `claim_id` integer: The ID of the insurance claim for this payment
    - `adjustment_type_id` integer: The ID of the adjustment type for this payment
    - `patient` APIV31EntitiesPatientBasic
      - `id` integer: User ID
      - `email` string: User email
      - `first_name` string: First name
      - `middle_name` string: Middle name
      - `last_name` string: Last name
      - `name` string: Full name
      - `created_at` string, date-time: User creation date in UTC
      - `updated_at` string, date-time: User last update date in UTC
      - `institution_id` integer: The institution this user belongs to
      - `foreign_id` string: Identifier NexHealth uses to uniquely match this record to its counterpart in the integrated EHR. How it is derived differs between EHRs and may change; treat it as an opaque string and do not parse it.
      - `foreign_id_type` string: Foreign ID type is a unique string identifier for the integrated system
      - `inactive` boolean: Is the user inactivated?
      - `home_phone_number` string: Home phone number
      - `work_phone_number` string: Work phone number
      - `work_phone_extension` string: Work phone extension
      - `cell_phone_number` string: Cell phone number. When the integrated system reports the patient's main number as an untyped primary number instead of a typed cell number — which is how most systems report it back after a write — this field falls back to that primary number. The fallback is usually the cell number, but the integrated system does not guarantee the primary number is a cell number.
      - `preferred_phone_number` string: The best-known phone number for reaching the patient: the first available of the integrated system's untyped primary number, cell phone number, home phone number, and work phone number. Read-only — write one of the typed phone number fields to change it.
      - `guarantor_id` integer: User ID of this patient's responsible party
      - `billing_type` string: Used by practices in some integrated systems to categorize and filter patients when creating reports, requesting payments, and performing other related office tasks. Some integrated systems call this an account type rather than a billing type
      - `chart_id` string: User-facing ID for referencing patient data, used in some integrated systems. Depending on the system, the chart ID supplements or replaces the foreign_id as the ID visible to EHR users
      - `preferred_language` string: Patient's preferred language as an ISO 639-1 code, if specified in the integrated system
      - `provider_id` integer: User ID of this patient's primary provider
      - `gender` string: Gender from biographical data
      - `new_patient` boolean: Whether the patient is new
      - `non_patient` boolean: Whether this is a non-patient user record
      - `date_of_birth` string: Date of birth in YYYY-MM-DD format
      - `premedication` string: Premedication notes
      - `address` APIV2EntitiesPatientAddress
        - `line_1` string, nullable: Address line 1
        - `line_2` string, nullable: Address line 2
        - `postal_code` string, nullable: Zip code
        - `city` string, nullable: City
        - `region` string, nullable: State
    - `provider` APIV31EntitiesProvider
      - `id` integer: User ID
      - `email` string: User email
      - `first_name` string: First name
      - `middle_name` string: Middle name
      - `last_name` string: Last name
      - `name` string: Full name
      - `created_at` string, date-time: User creation date in UTC
      - `updated_at` string, date-time: User last update date in UTC
      - `institution_id` integer: The institution this user belongs to
      - `foreign_id` string: Identifier NexHealth uses to uniquely match this record to its counterpart in the integrated EHR. How it is derived differs between EHRs and may change; treat it as an opaque string and do not parse it.
      - `foreign_id_type` string: Foreign ID type is a unique string identifier for the integrated system
      - `inactive` boolean: Is the user inactivated?
      - `phone_number` string: Primary phone number
      - `cell_phone_number` string: Cell phone number
      - `home_phone_number` string: Home phone number
      - `work_phone_number` string: Work phone number
      - `work_phone_extension` string: Work phone extension
      - `display_name` string: Display name
      - `npi` string: National Provider Identifier as registered in NPPES. May be null if the practice did not enter it into the integrated system.
      - `tin` string: Taxpayer Identification Number (SSN or ITIN). May be null if the practice did not enter it into the integrated system.
      - `state_license` string: State license number. May be null if the practice did not enter it into the integrated system.
      - `specialty_code` string: Specialty code corresponding to the provider's state license and NPI. May be null if the practice did not enter it into the integrated system.
    - `guarantor` APIV31EntitiesPatientBasic
      - `id` integer: User ID
      - `email` string: User email
      - `first_name` string: First name
      - `middle_name` string: Middle name
      - `last_name` string: Last name
      - `name` string: Full name
      - `created_at` string, date-time: User creation date in UTC
      - `updated_at` string, date-time: User last update date in UTC
      - `institution_id` integer: The institution this user belongs to
      - `foreign_id` string: Identifier NexHealth uses to uniquely match this record to its counterpart in the integrated EHR. How it is derived differs between EHRs and may change; treat it as an opaque string and do not parse it.
      - `foreign_id_type` string: Foreign ID type is a unique string identifier for the integrated system
      - `inactive` boolean: Is the user inactivated?
      - `home_phone_number` string: Home phone number
      - `work_phone_number` string: Work phone number
      - `work_phone_extension` string: Work phone extension
      - `cell_phone_number` string: Cell phone number. When the integrated system reports the patient's main number as an untyped primary number instead of a typed cell number — which is how most systems report it back after a write — this field falls back to that primary number. The fallback is usually the cell number, but the integrated system does not guarantee the primary number is a cell number.
      - `preferred_phone_number` string: The best-known phone number for reaching the patient: the first available of the integrated system's untyped primary number, cell phone number, home phone number, and work phone number. Read-only — write one of the typed phone number fields to change it.
      - `guarantor_id` integer: User ID of this patient's responsible party
      - `billing_type` string: Used by practices in some integrated systems to categorize and filter patients when creating reports, requesting payments, and performing other related office tasks. Some integrated systems call this an account type rather than a billing type
      - `chart_id` string: User-facing ID for referencing patient data, used in some integrated systems. Depending on the system, the chart ID supplements or replaces the foreign_id as the ID visible to EHR users
      - `preferred_language` string: Patient's preferred language as an ISO 639-1 code, if specified in the integrated system
      - `provider_id` integer: User ID of this patient's primary provider
      - `gender` string: Gender from biographical data
      - `new_patient` boolean: Whether the patient is new
      - `non_patient` boolean: Whether this is a non-patient user record
      - `date_of_birth` string: Date of birth in YYYY-MM-DD format
      - `premedication` string: Premedication notes
      - `address` APIV2EntitiesPatientAddress
        - `line_1` string, nullable: Address line 1
        - `line_2` string, nullable: Address line 2
        - `postal_code` string, nullable: Zip code
        - `city` string, nullable: City
        - `region` string, nullable: State
    - `claim` APIV2EntitiesLedgerInsuranceClaimBasic
      - `id` integer: Insurance Claim ID
      - `location_id` integer: Location ID
      - `patient_id` integer: Patient ID
      - `provider_id` integer: Provider ID
      - `guarantor_id` integer: User ID of the patient's responsible party
      - `subscription_id` integer: ID of the patient's insurance subscription
      - `status` 'draft' | 'sent' | 'received' | 'approved' | 'paid' | 'rejected' | 'canceled': Insurance Claim status
      - `finalized_at` string, date-time: Time in UTC when claim was closed
      - `sent_at` string, date-time: Time in UTC when claim was sent
      - `note` string: Note associated with the claim
      - `payment_estimate_total` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
      - `write_off_estimate_total` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
      - `write_off_total` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
      - `deleted_at` string, date-time: Deleted time for item in UTC
    - `charge` APIV2EntitiesPatientLedgerCharge
      - `id` integer: Resource ID
      - `foreign_id` string: Identifier NexHealth uses to uniquely match this record to its counterpart in the integrated EHR. How it is derived differs between EHRs and may change; treat it as an opaque string and do not parse it.
      - `location_id` integer, nullable: The ID of the location that this item is for
      - `patient_id` integer, nullable: The ID of the patient that this item is for
      - `guarantor_id` integer, nullable: The ID of the guarantor that this item is for
      - `provider_id` integer, nullable: The ID of the provider that this item is for
      - `updated_at` string, date-time: Last updated time for item in UTC
      - `description` string, nullable: A description of the item
      - `deleted_at` string, date-time, nullable: Deleted time for item in UTC
      - `fee` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
      - `charged_at` string, date: The UTC date charge was made
      - `procedure_id` string: The ID of the procedure associated with this charge
      - `claim_ids` integer[]: Insurance claim IDs associated with this charge
      - `payment_estimate_total` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
      - `write_off_estimate_total` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
      - `write_off_total` APIV2EntitiesPrice
        - `amount` string: The currency value, in whole units (e.g. dollars)
        - `currency` string: The ISO currency code
    - `adjustment_type` APIV20240412EntitiesLedgerAdjustmentType
      - `id` integer: Resource ID
      - `name` string: The name of the payment type
      - `active` boolean: Whether the adjustment type is currently active
      - `action` 'credit' | 'debit' | 'unknown': Indicates if this type will credit or debit the adjustment. Unknown option is for EHRs which doesn't support the concept
      - `updated_at` string, date-time: Adjustment Type update date in UTC
  - `count` integer: Number of total objects, in case of collection.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `500`: Internal Server Error

---

[API](https://skmtc.dev/nexhealth/apis/nexhealth-api-v3-1-0-beta.md) - [All operations](https://skmtc.dev/nexhealth/apis/nexhealth-api-v3-1-0-beta/llms.txt) - [OpenAPI document](https://skmtc.dev/nexhealth/apis/nexhealth-api-v3-1-0-beta/revisions/93cb4af790a5?raw)
