SDKs

Seven official client SDKs wrap the same REST contract these docs describe — and the API stays curl-first, so nothing here needs one.

Every example in these docs shows curl, because the API is plain REST with bearer-token auth: any language's HTTP client works. The SDKs exist to spare you the boilerplate — typed request/response shapes, the typed error taxonomy (validation, auth, permission, not-found, rate-limit), and HMAC request signing computed for you.

Languages

Each SDK is an idiomatic port of the Node reference client — same calls, same wire contract, local naming conventions.

What they cover

All seven expose the same surface, the endpoints an API key or OAuth token can reach:

• Create a session, read one back, and poll its live status (sessions.create, sessions.get, sessions.status).
• Revive an expired invitation in place, or issue a brand-new link that kills the old one, optionally switching the channel or recipient (sessions.reshare).
• Guest protection: read the current password or rotating code, change it after creation, and clear a lockout with or without rotating the secret.
• Mint agent-view tokens so your own UI can embed the live viewer.
• List a session's snapshots and fetch one as base64 PNG.
• Verify the current OAuth token, and exchange an authorization code for one (a standalone function — it runs before any client exists).
• Optional HMAC request signing: set a signing secret and every request carries the X-SeeItLive-Signature and X-SeeItLive-Timestamp headers.