SDKs
The fastest way to build on OrderFill.
Use an SDK unless you have a reason not to. Each one handles the three things you would otherwise get wrong:
- An idempotency key on every order, so a retry never opens a second position.
- Retries only where they help: rate limits and our own errors, with backoff. Refusals are not retried, because the answer will not change.
- Errors you can act on, carrying the code, the request ID and the hint.
Every SDK is built from the same written contract and tested against the same scenario, so a method behaves the same in every language.
| Language | Package | |
|---|---|---|
| TypeScript | @orderfill/sdk | Guide |
| Python | orderfill | Guide |
| Rust | orderfill | Guide |
| AI assistants (MCP) | @orderfill/mcp | Guide |
One contract, every language shows each operation's name in each.
Writing your own client
The API is plain JSON over HTTPS with a published contract at /v1/openapi.json.
If you generate a client from it, add by hand the three things above: send
Idempotency-Key on orders, retry only 429 and 5xx, and show details.hint.