A first-party Python SDK is on the roadmap, not yet shipped. Python backends, data pipelines, and ML workflows can call the public REST API today with the same scoped-key model as every other client; the SDK will be a thin wrapper when it lands, not a different shape.
Install (planned)
The package is not yet published. The planned name is fabricbloc:
# Planned, not yet available:
# pip install fabricblocPlanned baseline
- Python 3.11+ (planned baseline)
- Sync and async clients on the roadmap
- Typed via stubs from the same OpenAPI source as the TypeScript SDK
Use the REST API today
Every capability the SDK will eventually wrap is already available through the public REST API. The shape will not change — code written today against the REST surface keeps working when the SDK lands.
Same scoped-key model
Issue a scoped key from the console (or the TypeScript SDK), then call api.fabricbloc.com directly with an Authorization: Bearer <token> header. No special SDK is needed for production usage.
Shipping cadence
SDKs are prioritized by direct customer pull. Swift, Kotlin, and TypeScript are GA because mobile and JS are the highest-leverage surfaces today. Python is next as backend pull grows.
FAQ
When will the Python SDK ship?
No committed date. It is on the roadmap and gets prioritized by direct customer pull. Share your use case via the contact form and we will queue accordingly.
Can I use Python today?
Yes — the public REST API at api.fabricbloc.com covers every capability the future SDK will wrap. Use requests or httpx with a scoped Authorization: Bearer key. The shape will not change between the REST surface and the SDK once it ships.
Is there an OpenAPI spec to generate a client from?
Yes. Start from the generated REST API reference. Automation can discover the machine-readable service contracts through the site's agent discovery files.