Charges
Query billing charges without worrying about Tebra's server-side 60-day query limit.
- Resource
client.charges- SOAP operation
GetCharges- Flat method
get_charges- Writes
- None
On this page
Methods
client.charges.list#
readasync list(*, practice_name=None, practice_id=None, patient_name=None, from_service_date=None, to_service_date=None, from_posting_date=None, to_posting_date=None, from_created_date=None, to_created_date=None, from_last_modified_date=None, to_last_modified_date=None, procedure_code=None, diagnosis_code=None, encounter_status=None, status=None, batch_number=None, billed_to=None, case_payer_scenario=None, rendering_provider_full_name=None, referring_provider_full_name=None, scheduling_provider_full_name=None, service_location_name=None, include_unapproved_charges=None, auto_chunk_days=60, fields=None, extra_filter=None) -> list[dict]Query billing charges using GetCharges. When both service dates are supplied and span more than auto_chunk_days days (default 60), the wrapper splits the range into contiguous windows, queries each one, and deduplicates the merged rows by charge ID. Set auto_chunk_days=None to send a single request.
Parameters
| Parameter | Type | Description |
|---|---|---|
practice_name | str | None | Practice name filter. |
practice_id | int | str | None | Practice ID; resolved to PracticeName. |
patient_name | str | None | Patient name filter. |
from_service_date | str | date | datetime | None | Lower service date. |
to_service_date | str | date | datetime | None | Upper service date. |
from_posting_date | str | date | datetime | None | Lower posting date. |
to_posting_date | str | date | datetime | None | Upper posting date. |
from_created_date | str | date | datetime | None | Lower creation-date bound. |
to_created_date | str | date | datetime | None | Upper creation-date bound. |
from_last_modified_date | str | date | datetime | None | Lower last-modified bound. |
to_last_modified_date | str | date | datetime | None | Upper last-modified bound. |
procedure_code | str | None | CPT/HCPCS procedure code. |
diagnosis_code | str | None | Diagnosis code. |
encounter_status | str | None | Encounter status filter. |
status | str | None | Charge status filter. |
batch_number | str | None | Batch number filter. |
billed_to | str | None | Billed-to filter. |
case_payer_scenario | str | None | Case payer scenario filter. |
rendering_provider_full_name | str | None | Rendering provider name. |
referring_provider_full_name | str | None | Referring provider name. |
scheduling_provider_full_name | str | None | Scheduling provider name. |
service_location_name | str | None | Service location name. |
include_unapproved_charges | bool | str | None | Include unapproved charges. Booleans become true/false. |
auto_chunk_days | int | None | Maximum inclusive window size. Default 60; None disables chunking. |
fields | Iterable[str] | Mapping[str, bool] | None | Field selector. |
extra_filter | Mapping[str, Any] | None | Additional raw Filter keys applied to every window. |
Returns
list[dict[str, Any]] deduplicated by ID when chunked.Example
# A 106-day range is split into <=60-day windows automatically.
charges = await client.get_charges(
practice_id=7,
from_service_date="2026-01-01",
to_service_date="2026-04-16",
)
# Disable chunking explicitly
raw = await client.charges.list(
practice_id=7,
from_service_date="2026-01-01",
to_service_date="2026-04-16",
auto_chunk_days=None,
)Automatic windowing
Normalize both datesAccepts
date, datetime, or string formats.Split into windowsUses
chunk_date_range with at most 60 inclusive days per window.Query sequentiallyEach window is fetched through the normal throttled path.
Merge and deduplicateRows are merged and deduplicated by charge
ID.Filters apply to every windowAll other filters (
patient_name, procedure_code, provider names, and so on) are forwarded unchanged to every window.from tebra_soap_api.utils import chunk_date_range
# The same helper the resource uses
windows = chunk_date_range("2026-01-01", "2026-03-15", max_days=60)
print(windows) # [("2026-01-01", "2026-03-01"), ("2026-03-02", "2026-03-15")]