Skip to main content
FastAPI dependencies are a good place to resolve the authenticated application user before Praxa is called. Pydantic then bounds the request shape.

Prerequisites

Before you begin, prepare:
  • a trusted server runtime and application authentication boundary;
  • a disposable personal workspace Praxa key with only the tutorial’s required scopes;
  • synthetic input plus a persisted application request ID for replay tests;
  • a fake upstream for unit tests and a non-production environment for canaries;
  • an acceptance assertion that proves the FastAPI dependency boundary admits one task and maps failures without leaking upstream data.

1. Install dependencies

2. Implement the route

app/main.py
The application user comes from require_user, not the body. Do not include the upstream response text in a production exception unless you have explicitly redacted it.

3. Test with dependency overrides

tests/test_tasks.py
Intercept HTTPX for valid-route tests and assert the outgoing URL, bounded body, server-owned authorization header, and deterministic idempotency key. Add a separate dependency override that raises 401 and prove there is no upstream call.

4. Run the live acceptance check

Against staging, submit one disposable task twice with the same requestId. Require the same logical run, then poll that run to a terminal state. Revoke the test key after cleanup.

Troubleshooting

Best practices

  • Create one AsyncClient at application startup and close it at shutdown.
  • Resolve the user with a dependency before calling Praxa.
  • Bound Pydantic models and request-body size.
  • Do not include tenant, owner, scope, or Praxa key in the request model.
  • Keep error details redacted and responses no-store.
  • Use HTTPX MockTransport for unit tests and disposable keys for canaries.

FastAPI testing

Use the official TestClient and pytest guidance for the application boundary.

Optimize for production

  • Reuse one configured HTTP or SDK client per process and bound concurrent upstream work.
  • Prefer durable admission plus asynchronous readback over holding application requests open.
  • Cache only non-sensitive, tenant-scoped reads within their documented freshness window.
  • Measure p50/p95 latency, admission-to-terminal time, retries, conflicts, and connection reuse before tuning.
Optimize only after the correctness and isolation matrix passes. Lower latency or cost is not an improvement if verified outcomes, authority checks, or recovery rates regress.

Cleanup and next steps

  1. Revoke the disposable Praxa key and require a later request to fail.
  2. Remove synthetic application records and any temporary environment files.
  3. Cancel or archive unresolved test runs according to the application policy.
  4. Retain only redacted request, run, and verification identifiers needed for the test record.
After cleanup, run the shared integration test matrix and record any environment-specific check that remains pending.

Frequently asked questions

What proves this tutorial works?

The minimum observable result is that the FastAPI dependency boundary admits one task and maps failures without leaking upstream data. A compile, package import, mocked response, or initial admission alone does not prove the complete workflow.

Can a browser, mobile app, or model prompt hold the credential?

No. Browser and mobile bundles are inspectable. Keep the Praxa credential in the trusted application backend.

How should an ambiguous mutation be retried?

Persist the exact logical input and idempotency key before the first attempt. Reconcile through authoritative readback or replay the exact request with that same key before creating new work.

What should we monitor after release?

Monitor application auth failures, upstream status/code, latency, retries, replay conflicts, and terminal run outcomes. Alert on authorization bypass, cross-tenant disclosure, repeated conflicts, or cleanup failure.
Last modified on August 14, 2026