SDK Overview
Choose the right PacSpace SDK and understand version support.
PacSpace SDKs wrap the same Balance API.
Pick the SDK that matches the service that records usage.
Choose Your SDK
| SDK | Package | Best For | Docs Target |
|---|---|---|---|
| TypeScript | @pacspace-io/sdk | Node.js services, TypeScript backends, webhook handlers | 0.7.0 |
| Python | pacspace-sdk | Python APIs, jobs, billing workers, data pipelines | 0.2.0 |
Both SDKs support the core Recordation flow:
- Record usage with
emit. - Wait for verification when needed.
- Derive a balance.
- Compare both sides' views.
- Checkpoint the period.
- Verify webhooks.
Host Configuration
Docs examples use:
https://app.pacspace.io
Pass that host explicitly when you want the SDK client pinned to the public endpoint shown in these docs.
For Sandbox, use a pk_test_* key and the Sandbox URL from your PacSpace dashboard.
Version Policy
SDKs follow semantic versioning.
| Change Type | What To Expect |
|---|---|
| Patch | Bug fixes and documentation clarifications |
| Minor | New helpers or new public fields that do not break existing integrations |
| Major | Breaking API changes with migration notes |
Every major SDK release needs a matching docs update before it is promoted as current.
Parity
The TypeScript SDK has the widest helper surface today. The Python SDK covers the main flow and will add helper parity over time.
Current known gaps in Python 0.2.0:
receipts.*receipt-document helpers by receipt ID- checkpoint timeline helpers
- checkpoint diff helpers
The REST API remains the source of truth. If an SDK helper is not available yet, call the documented endpoint directly.