SDKs
SDK strategy for the DMTR API.
SDK Strategy
Official SDKs for TypeScript and Python are planned for Q3 2026. Until then, use the REST API directly — it is designed to be SDK-simple.
The DMTR API follows consistent patterns across all endpoints: JSON request/response bodies, standard HTTP status codes, idempotency keys, and typed error responses. Most integrations can be built with a standard HTTP client and the Position Object schema.
Using the API directly
curl -X POST https://api.dmtr.ai/v1/transfers/evaluate \
-H "Authorization: Bearer $DMTR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"position_id": "pos-meg-2026-001",
"buyer_id": "part-buyer-001"
}'See the API Overview for authentication, base URLs, and conventions. The First API Call quickstart walks through a complete request/response cycle.
Planned SDKs
| Language | Status | Target | Features |
|---|---|---|---|
| TypeScript | Planned | Q3 2026 | Typed Position Objects, Rights Engine client, streaming events |
| Python | Planned | Q3 2026 | Data pipeline integration, pandas-compatible position queries |
Community
Community-maintained clients are welcome. If you build one, open an issue on the DMTR GitHub and we will list it here.