Skip to main content

reflectapi-runtime

Runtime support library for Python clients generated by reflectapi. Generated code imports from reflectapi_runtime; you don't normally call this library directly.

What it provides

  • ClientBase / AsyncClientBase — base classes used by the generated Client / AsyncClient. They wrap httpx and handle request build-up, Pydantic-based response validation, and middleware.
  • ApiResponse[T, E, H] — typed wrapper around the response value, transport metadata, the optional typed error, and the API's declared response headers (.headers).
  • ApiStream[T, H] / AsyncApiStream[T, H] — iterators returned by streaming methods, exposing the response's metadata and declared headers once iteration starts.
  • ApplicationError, NetworkError, TimeoutError, ValidationError — exceptions raised by the generated methods on non-2xx, transport, and validation failures respectively.
  • ReflectapiPartialModel — base class for generated models with three-state fields (value / explicit-null / absent) so absent and explicit-null can round-trip, tracked via Pydantic's model_fields_set.
  • Authentication helpers (BearerTokenAuth, APIKeyAuth, BasicAuth, OAuth2ClientCredentialsAuth, OAuth2AuthorizationCodeAuth).
  • Middleware, batching, and testing utilities (MockClient, CassetteMiddleware).

Streaming endpoints

Endpoints declared with Builder::stream_route on the server are exposed on the generated client as ordinary methods that return an iterator:

async with AsyncClient("http://localhost:3000") as client:
    async for event in client.pets.cdc_events(headers=headers):
        ...  # process each event

The sync client returns a regular Iterator; both validate each event against the declared item model. The wire format is Server-Sent Events (data: <json>\n\n); init failures (4xx/5xx) raise ApplicationError and do not enter the iterator. Breaking out of the loop or calling stream.aclose() releases the underlying HTTP connection.

Validation is strict: an event whose payload doesn't match the item model (for example, an unknown discriminated-union variant added by a newer server) raises ValidationError mid-stream and the iterator terminates. Items received before the bad event are still delivered.

Compatibility

Python 3.12+. The package targets the same reflectapi minor version as the schema you generate from; mismatches will surface at import time.

Metadata

Release files for reflectapi-runtime 0.19.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for reflectapi-runtime 0.19.0
File Size Uploaded
reflectapi_runtime-0.19.0.tar.gz 71.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for reflectapi-runtime 0.19.0
File Interpreter ABI Platform
reflectapi_runtime-0.19.0-py3-none-any.whl Python 3 none any Details

Total release size: 111.6 kB

Release files / reflectapi_runtime-0.19.0.tar.gz

Download URL reflectapi_runtime-0.19.0.tar.gz
Size 71.2 kB
Tags Source
SHA-256 checksum
How to use checksums
5b69d30220f05c88791a947e07fc1820ab25b52bd1f00f5ffbf9be9ac7c96847
BLAKE2b-256 checksum
How to use checksums
7a56574a63b4f64bbe5d88831993eba68e3c08ef536ea034f1a4207f3c56ff79
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release files / reflectapi_runtime-0.19.0-py3-none-any.whl

Download URL reflectapi_runtime-0.19.0-py3-none-any.whl
Size 40.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c529ac98e92e6738b787d9928edaa6d7a6309901f6229e6c4bb99f37983d06ad
BLAKE2b-256 checksum
How to use checksums
16219766f8d5f3dc3f47f0b625efced70b626277afc0a23e271155188799940d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page