CL2C API reference
Everything your software can do with Taliware: manage contracts, invite users, issue digital assets, and check credits.
New to the API? Follow the quick start first — it walks through the four calls most integrations need. Unfamiliar terms are explained in Key concepts.
Before you start
1. Where requests go
Every path below starts with this address.
https://developer.taliware.com/api/v12. Prove who you are
Send your API key in a header on every request. Keep it on your server.
x-api-key: YOUR_API_KEY3. Send and receive JSON
Add Content-Type: application/json when you send a body. Lists come back as data plus pagination; use ?page= and ?limit= to move through them.
4. Read errors
Errors always have the same shape, with a human-readable message.
{ "error": "…", "details": ["…"] }What the status codes mean
- 200 / 201
- It worked. 201 means something new was created.
- 207
- Bulk request: some items worked and some didn't. Check each result.
- 400
- Something in your request is missing or invalid. The message says what.
- 401
- The API key is missing, wrong, or deleted.
- 403
- The key is valid but isn't allowed to do this.
- 404
- That item doesn't exist in this organization.
- 409
- It already exists (for example, a user who's already invited).
- 500 / 503
- A problem on our side. Wait a moment and try again.