SDKs

Official client libraries are planned but not published yet. The API is two JSON endpoints, so calling it directly is straightforward — server-side only, never from the browser.

Recommended today

Use plain HTTP from your backend. Both snippets use placeholders only.

capture.ts — JavaScript fetch

const response = await fetch("https://sessionshot.com/api/captures", {
  method: "POST",
  headers: {
    Authorization: "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    url: "https://example.com",
    output: { format: "png", fullPage: true },
  }),
})

const capture = await response.json()

terminal — curl

curl -X POST "https://sessionshot.com/api/captures" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com" }'

Server-side only

API keys must never ship in frontend or browser code. Call the API from your backend, a job runner, or CI.

Planned SDKs

No install commands are published because no packages exist yet — anything claiming to be a SessionShot SDK today is not ours.

Node.js

A typed client for creating captures, polling status, and handling signed URLs — first on the roadmap.

Python

Under consideration after Node.js, based on private-beta demand.

In the meantime

API referenceFull request/response schemas and a polling example.Dashboard quickstartCopyable snippets with your live workspace state (sign-in required).