Livstick Client API V2.1
API 2.1 is the V2 surface Livstick keeps running in production, not a deprecated one: it sits on the same key management as v3 — hashed secrets, expiry, status, audit and scope enforcement — and only its shapes are inherited. Each operation below has its own page, generated from the specification the service publishes, so it stays exact as the surface evolves. Two things the specification cannot tell you on its own: the base URL is not published here, it is provided with your access; and details is a POST even though it only reads, a habit carried over from the original V2 design.
- Version
- 2.1.0
- Authentication
- API key in the path
The API key is intentionally kept in the path for V2 compatibility:
/v2.1/client/{key}/{crid}/... or /v2.1/user/{key}/{crid}/....
Client routes require the client_v2 scope. User routes require the user_v2
scope. Unknown, expired, revoked, malformed, or wrong-scope keys return the
legacy JSON error envelope.
health
Service health endpoints.
client
Client-scoped V2.1 operations.
-
Method GET
/v2.1/client/{key}/{crid}/redirectCreate or return recording URLs -
Method POST
/v2.1/client/{key}/{crid}/retargetCreate or return a retargetable CRID -
Method GET
/v2.1/client/{key}/{crid}/qrcodeDownload a QR code -
Method POST
/v2.1/client/{key}/{crid}/qrcodeDownload a QR code with JSON options -
Method GET
/v2.1/client/{key}/{crid}/cardDownload a PDF card -
Method POST
/v2.1/client/{key}/{crid}/notifyMark the message as delivered -
Method POST
/v2.1/client/{key}/{crid}/modifyModify container metadata -
Method POST
/v2.1/client/{key}/{crid}/detailsGet legacy message details -
Method POST
/v2.1/client/{key}/{crid}/webhook/{webhookId}Process a supported legacy webhook
user
User-scoped redirect operation.
docs
Embedded OpenAPI and Swagger UI.