Skip to main content

varco-fastapi

PyPI version Python License: Apache 2.0 GitHub

FastAPI integration and HTTP client utilities for varco.

Provides structured HTTP connection configuration, TLS trust-store management, JWT authority, and HTTP middleware wiring on top of FastAPI and httpx. Requires varco-core.


Install

pip install varco-fastapi

HTTP connection settings

HttpConnectionSettings is a structured config object that produces kwargs for httpx.AsyncClient (or httpx.Client).

Unlike the Postgres/Redis/Kafka settings, there is no fixed env-var prefix. A service typically calls many different external HTTP APIs — a hardcoded HTTP_ prefix would only allow one of them to be configured from env vars at a time. Instead, you supply a prefix when loading from env:

payment = HttpConnectionSettings.from_env(prefix="PAYMENT_API_")
notify = HttpConnectionSettings.from_env(prefix="NOTIF_API_")

Plain connection (no auth, no TLS)

import httpx
from varco_fastapi.connection import HttpConnectionSettings

# Direct construction — no env vars read
conn = HttpConnectionSettings(base_url="https://api.example.com/v1", timeout=10.0)

async with httpx.AsyncClient(**conn.to_httpx_kwargs()) as client:
    response = await client.get("/users")

From environment variables (multi-client)

# Payment API
PAYMENT_API_BASE_URL=https://pay.example.com/v1
PAYMENT_API_TIMEOUT=5.0

# Notification API
NOTIF_API_BASE_URL=https://notify.example.com
NOTIF_API_TIMEOUT=10.0
payment = HttpConnectionSettings.from_env(prefix="PAYMENT_API_")
notify = HttpConnectionSettings.from_env(prefix="NOTIF_API_")

async with httpx.AsyncClient(**payment.to_httpx_kwargs()) as client:
    await client.post("/charge", json={"amount": 9.99})

You can also configure via host and port instead of a full URL:

MY_SVC_HOST=api.example.com
MY_SVC_PORT=8080
# effective base_url → "http://api.example.com:8080"

With Basic authentication

from varco_core.connection import BasicAuthConfig

conn = HttpConnectionSettings(
    base_url="https://api.example.com",
    auth=BasicAuthConfig(username="svc-user", password="secret"),
)
# to_httpx_kwargs() includes auth=("svc-user", "secret") automatically

async with httpx.AsyncClient(**conn.to_httpx_kwargs()) as client:
    response = await client.get("/protected")

From env:

MY_SVC_BASE_URL=https://api.example.com
MY_SVC_AUTH__TYPE=basic
MY_SVC_AUTH__USERNAME=svc-user
MY_SVC_AUTH__PASSWORD=secret
conn = HttpConnectionSettings.from_env(prefix="MY_SVC_")

With OAuth2 static bearer token

from varco_core.connection import OAuth2Config

conn = HttpConnectionSettings(
    base_url="https://api.example.com",
    auth=OAuth2Config(token="eyJhbGciOiJSUzI1NiJ9..."),
)
# OAuth2 is NOT injected into kwargs automatically — httpx has no built-in
# OAuth2 flow.  Add the Authorization header via a middleware or event hook:
async with httpx.AsyncClient(**conn.to_httpx_kwargs()) as client:
    response = await client.get(
        "/protected",
        headers={"Authorization": f"Bearer {conn.auth.token}"},
    )

Note: For OAuth2 client-credentials flows (token refresh), use an httpx event hook or middleware — HttpConnectionSettings is a pure config object and does not manage token lifecycle.

With TLS / SSL (custom CA)

from varco_core.connection import SSLConfig
from pathlib import Path

ssl = SSLConfig(ca_cert=Path("/etc/ssl/api-ca.pem"), verify=True)
conn = HttpConnectionSettings.with_ssl(
    ssl,
    base_url="https://secure-api.example.com",
)
# to_httpx_kwargs()["verify"] → ssl.SSLContext built from the CA cert

async with httpx.AsyncClient(**conn.to_httpx_kwargs()) as client:
    response = await client.get("/data")

From env:

MY_SVC_BASE_URL=https://secure-api.example.com
MY_SVC_SSL__CA_CERT=/etc/ssl/api-ca.pem
MY_SVC_SSL__VERIFY=true
conn = HttpConnectionSettings.from_env(prefix="MY_SVC_")

Disable TLS verification (dev / testing only)

ssl = SSLConfig(verify=False, check_hostname=False)
conn = HttpConnectionSettings.with_ssl(ssl, base_url="https://localhost:8443")
# to_httpx_kwargs()["verify"] → False

With mTLS (client certificates)

ssl = SSLConfig(
    ca_cert=Path("/etc/ssl/ca.pem"),
    client_cert=Path("/etc/ssl/client.crt"),
    client_key=Path("/etc/ssl/client.key"),
)
conn = HttpConnectionSettings.with_ssl(ssl, base_url="https://mtls-api.example.com")
async with httpx.AsyncClient(**conn.to_httpx_kwargs()) as client:
    response = await client.get("/secure")

Bridge to TrustStore (legacy ClientProfile)

trust_store = conn.to_trust_store()  # None when ssl is not set
# use with ClientProfile.production(trust_store=trust_store)

Connection settings reference

All field names below assume a prefix of MY_SVC_ — replace it with your own.

Env var Default Description
{PREFIX}HOST localhost API hostname (used when BASE_URL is empty)
{PREFIX}PORT 443 API port (used when BASE_URL is empty)
{PREFIX}BASE_URL (empty) Full base URL — overrides host/port when set
{PREFIX}TIMEOUT 30.0 Default request timeout in seconds
{PREFIX}SSL__CA_CERT — Path to CA certificate
{PREFIX}SSL__CLIENT_CERT — Path to client certificate (mTLS)
{PREFIX}SSL__CLIENT_KEY — Path to client private key (mTLS)
{PREFIX}SSL__VERIFY true TLS peer verification (false = skip)
{PREFIX}AUTH__TYPE — basic or oauth2
{PREFIX}AUTH__USERNAME — Basic auth username
{PREFIX}AUTH__PASSWORD — Basic auth password
{PREFIX}AUTH__TOKEN — OAuth2 static bearer token

CRUD routers

VarcoCRUDRouter[D, PK, C, R, U] (and the pre-composed CRUDRouter / ReadOnlyRouter / WriteRouter / NoDeleteRouter presets in varco_fastapi.router.presets) is the service-backed router base — it injects an AsyncService, dispatches the standard CRUD actions, and auto-registers named tasks for ?with_async=true recovery.

from varco_fastapi.router.presets import CRUDRouter


class OrderRouter(CRUDRouter[Order, UUID, OrderCreate, OrderRead, OrderUpdate]):
    _prefix = "/orders"
    _service = container.get(OrderService)  # AsyncService[Order, UUID, C, R, U]
    _auth = container.get(JwtBearerAuth)

Typed concrete service (6th S type arg)

Add the concrete AsyncService subclass as an optional 6th type argument to get self._service typed ConcreteService | None and the self.service accessor typed non-Optional ConcreteService — custom service methods beyond the CRUD surface are then visible to the type checker with zero per-subclass boilerplate (no cast, no hand-rolled @property override):

from varco_fastapi.router.endpoint import route


class OrderService(AsyncService[Order, UUID, OrderCreate, OrderRead, OrderUpdate]):
    async def cancel_order(self, order_id: UUID) -> None: ...


class OrderRouter(CRUDRouter[Order, UUID, OrderCreate, OrderRead, OrderUpdate, OrderService]):
    _prefix = "/orders"

    @route("POST", "/{order_id}/cancel")
    async def cancel(self, order_id: UUID) -> None:
        # self.service is typed OrderService — .cancel_order is visible with no cast.
        await self.service.cancel_order(order_id)
  • 5-arg subscription (CRUDRouter[Order, UUID, OrderCreate, OrderRead, OrderUpdate]) keeps working unchanged — S is defaulted via PEP 696 (typing_extensions.TypeVar, since requires-python = ">=3.12" predates the native 3.13 syntax) and resolves to AsyncService[Any, ...].

  • self.service raises RuntimeError if _service was never injected/set — prefer it over self._service at call sites that invoke custom methods, so you don't repeat an is None guard. The 501-Not-Implemented CRUD fallback path is unaffected — it still reads _service directly, not this property.

  • Fallback idiom for anyone staying on 5 type args — declare a subclass @property that casts:

    from typing import cast
    
    
    class OrderRouter(CRUDRouter[Order, UUID, OrderCreate, OrderRead, OrderUpdate]):
        _prefix = "/orders"
        _service = container.get(OrderService)
    
        @property
        def order_service(self) -> OrderService:
            return cast(OrderService, self._service)
    

Service-free (generic) REST servers

Use GenericRouter when the server has no AsyncService or repository — for example a data-transformation pipeline, an API gateway, or computed analytics routes. All cross-cutting features (middleware, telemetry, auth, authorization) work identically.

from varco_fastapi.router.presets import GenericRouter
from varco_fastapi.router.endpoint import route
from varco_fastapi.auth import JwtBearerAuth
from varco_fastapi.auth.guard import require_scopes, require_roles, allow_anonymous


class ReportRouter(GenericRouter):
    _prefix = "/reports"
    _auth = JwtBearerAuth(...)

    # Requires scope — denies 403 if caller does not have "reports:read"
    @route("GET", "/summary", requires=require_scopes("reports:read"))
    async def get_summary(self, ctx) -> dict:
        return {"total": 42}

    # Requires role
    @route("DELETE", "/cache", requires=require_roles("admin"))
    async def purge_cache(self, ctx) -> None: ...

    # Public endpoint — allow_anonymous bypasses auth checks entirely
    @route("GET", "/status", requires=allow_anonymous())
    async def status(self, ctx) -> dict:
        return {"ok": True}


app = create_varco_app(routers=[ReportRouter])

Available guard helpers (varco_fastapi.auth.guard):

Helper Description
require_scopes(*s, all=True) All (or any) OAuth scopes must be present
require_roles(*r, all=True) All (or any) named roles must be present
require_grant(action, key) ctx.can(action, resource_key) must be True
require_token_profile(*names) Resolved JWT token profile must be one of names
require_predicate(fn) Custom sync/async callable returning bool
allow_anonymous() Anonymous callers pass through (public endpoints)

Custom @route handlers — full FastAPI parameters

A custom @route method may declare any parameter a normal FastAPI endpoint can, and FastAPI parses, validates, coerces and injects it — Query(...), Body(...) (Pydantic models), Depends(...), Request/Response/BackgroundTasks, and type-coerced path params. The return annotation drives the OpenAPI response model. ctx/auth/context still receive the router's AuthContext, and any RouteGuard still runs before the handler.

from fastapi import Body, Depends, Query, Request
from pydantic import BaseModel

from varco_core.auth.base import AuthContext


class SummaryFilter(BaseModel):
    since: str | None = None


class ReportRouter(GenericRouter):
    _prefix = "/reports"
    _auth = JwtBearerAuth(...)

    @route("POST", "/{report_id}/summary", requires=require_scopes("reports:read"))
    async def summary(
        self,
        report_id: int,  # typed path param — coerced to int
        ctx: AuthContext,  # injected from _auth
        window: int = Query(30, ge=1, le=365),  # validated query param (422 on bad input)
        filters: SummaryFilter = Body(...),  # Pydantic request body
        repo: Repo = Depends(get_repo),  # arbitrary FastAPI dependency
        request: Request = None,  # raw request if you want it
    ) -> SummaryResponse:  # → OpenAPI response model
        ...

Under the hood build_router() synthesizes a wrapper whose __signature__ mirrors the method, so FastAPI drives all parsing natively — no manual request handling needed.


JWT authentication — foreign claim shapes, token profiles, hardening

JwtBearerAuth verifies a Bearer JWT via TrustedIssuerRegistry and builds an AuthContext from it. As of the claim-transformer + token-profile layer (varco_core.jwt), this happens automatically even when the token was minted by a third-party IdP with a different claim shape (Keycloak's realm_access.roles, Cognito's token_use, a bespoke sofy-roles claim, …) — see technical_docs/features/jwt-claim-transformer.md for the full env-var reference and per-issuer recipes.

from varco_fastapi.auth import JwtBearerAuth

# Hardened: enforce this service's audience + tolerate 30s of clock skew.
# Both also read from VARCO_JWT_AUDIENCE / VARCO_JWT_LEEWAY_SECONDS when omitted.
auth = JwtBearerAuth(registry, audience="orders-api", leeway=30.0)

audience=None (the default) does not enforce aud — JwtBearerAuth logs one warning at construction time when this is the case. Set an explicit audience= (or VARCO_JWT_AUDIENCE) to reject tokens minted for a different service.

Named token profiles — replacing SYSTEM_ISSUER

A deployment can recognise more than one kind of trusted internal/system token (system, internal, partner, service-mesh, …) via env-declared TokenProfiles, and gate a route on the resolved profile with require_token_profile():

from varco_fastapi.router.presets import GenericRouter
from varco_fastapi.router.endpoint import route
from varco_fastapi.auth import JwtBearerAuth
from varco_fastapi.auth.guard import require_token_profile

# VARCO_JWT_PROFILE__INTERNAL__ISS=mesh-signer
# VARCO_JWT_PROFILE__INTERNAL__TOKEN_TYPE=system
# VARCO_JWT_PROFILE__INTERNAL__ROLES=internal


class MeshRouter(GenericRouter):
    _prefix = "/mesh"
    _auth = JwtBearerAuth(registry)

    @route("GET", "/internal-only", requires=require_token_profile("internal"))
    async def internal_only(self, ctx) -> dict:
        return {"ok": True}

See technical_docs/features/token-profiles.md for the full env var reference, precedence rules, and the SYSTEM_ISSUER deprecation note.


Composite / all-in-one deployment

Combine several independently-built services into a single deployable process without changing any of them. Each service keeps its own DIContainer, database, environment, middleware, and /docs — they are mounted side by side under path prefixes.

from varco_fastapi import create_composite_app, ServiceMount

from orders_service.app import app as orders_app  # its own create_varco_app()
from billing_service.app import app as billing_app  # its own container + DB

composite = create_composite_app(
    [
        ServiceMount("/orders", orders_app),
        ServiceMount("/billing", billing_app),
    ]
)
# uvicorn composite:composite
#   /orders/...   → orders service (own docs at /orders/docs)
#   /billing/...  → billing service (own docs at /billing/docs)
#   /health       → aggregate health across both services (503 if any is down)
#   /             → landing page listing each service

create_composite_app installs a CompositeLifespan that drives each sub-app's own lifespan — Starlette does not propagate lifespan into mounted apps, so this is what actually starts each service's DB pool / event bus / outbox relay. Startup is fail-fast (one broken service aborts the whole process); shutdown is LIFO.

All services share one os.environ. Runtime isolation is automatic; the only hazard is build-time env-name collisions. Either namespace env vars per service (ORDERS_DB_URL, BILLING_DB_URL) or use build_service for a scoped overlay:

from varco_fastapi import build_service

orders = build_service(
    "/orders", create_orders_app, env={"DATABASE_URL": "postgresql+asyncpg://.../orders"}
)
billing = build_service(
    "/billing", create_billing_app, env={"DATABASE_URL": "postgresql+asyncpg://.../billing"}
)
composite = create_composite_app([orders, billing])

See technical_docs/features/composite-deployment.md and examples/23-composite-all-in-one/ for the full reference.


Google A2A protocol (SkillAdapter)

SkillAdapter exposes any VarcoRouter — or, since Plan 005 Phase 7, any SkillSource — as a Google A2A agent, at the v1.0.0 surface (GET /.well-known/agent-card.json, POST /a2a JSON-RPC 2.0) plus the pre-v1.0.0 paths for one minor release (legacy_paths=True, the default).

from varco_fastapi.router.skill import SkillAdapter

adapter = SkillAdapter(
    OrderRouter,
    agent_name="OrderAgent",
    agent_description="Manages customer orders",
    client=OrderClient(base_url="http://localhost:8080"),
)
adapter.mount(app)  # /.well-known/agent-card.json + /a2a + legacy paths

Not backed by a router? Pass source= instead — a SkillSource (skills() / agent_metadata() / async invoke(skill_id, payload, *, ctx=)) decouples the adapter from VarcoRouter entirely, and ctx carries the verified caller's AuthContext through to your own invoke() implementation for auditing. Long-running skills reuse the existing async job machinery — pass job_runner/job_store and the response returns state: working immediately; pass conversation_store for multi-turn history.

See technical_docs/features/a2a-surface.md for the full v1.0.0 path/method table, a non-router SkillSource example, and the legacy-path deprecation timeline.


Related packages

Package Description
varco-core Domain model, service layer, JWT authority — required dependency
varco-sa SQLAlchemy async backend
varco-kafka Kafka event bus backend
varco-redis Redis event bus + cache backend

Links

Metadata

Release files for varco-fastapi 3.2.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 varco-fastapi 3.2.0
File Size Uploaded Provenance Actions
varco_fastapi-3.2.0.tar.gz 547.1 kB With provenance Details for varco_fastapi-3.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for varco-fastapi 3.2.0
File Interpreter ABI Platform Actions
varco_fastapi-3.2.0-py3-none-any.whl Python 3 none any Details for varco_fastapi-3.2.0-py3-none-any.whl

Total release size: 984.2 kB

Release files / varco_fastapi-3.2.0.tar.gz

Download URL varco_fastapi-3.2.0.tar.gz
Size 547.1 kB
Tags Source
SHA-256 checksum
How to use checksums
ae0fee20c9e44f668fad12f1bfdbd13b17df97f41da05f211b76af8c0e349abb
BLAKE2b-256 checksum
How to use checksums
31df83a882a8b86846042419ff9d9c0870212f31cc3c49f5dbc0574210ff8663
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 Sep 12, 2026.

Transparency log

Release files / varco_fastapi-3.2.0-py3-none-any.whl

Download URL varco_fastapi-3.2.0-py3-none-any.whl
Size 437.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2344b3e97bc9822bd3c83a964e21696e818a3930485e753631b751f420bdeeaa
BLAKE2b-256 checksum
How to use checksums
94504f898106ddfd243b76ce7df4b3655f6c516e1525774ae5f14176c8bb3936
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 Sep 12, 2026.

Transparency log

Security for varco-fastapi 3.2.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for varco_fastapi-3.2.0.tar.gz

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 Sep 12, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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