The plan snapshot for the connected workspace: the credit balance in
both units (1 credit is 1000 tokens), every plan ceiling, and current
storage and profile usage. A limit the plan does not cap is null,
which means unlimited.
Authorization
bearerAuth An API key created under Settings > API & Webhooks. Keys start with sf_live_.
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/workspace"{ "data": { "id": "k9WmT3xR2pQ7nV4bd", "name": "Acme Studio", "plan": "pro", "credits": { "credits": 42500, "tokens": 42500000 }, "limits": { "maxRendersPerMonth": 100, "maxAutomations": 5, "maxProfiles": 3, "maxVideoDurationSeconds": 900, "maxRenderSeconds": 900, "storageBytes": 21474836480, "watermark": false }, "usage": { "storageBytes": 3187441664, "profiles": 2 } }}Library counts and quota usage GET
How much of the plan is used right now: the number of videos, automations and clips in the library, generations and renders started in the last 30 days against their monthly ceiling, storage, credits, and the per-video duration and render-time caps. `since` is the start of the rolling window the counters cover.
Get a download URL GET
A URL for the finished mp4 that is known to resolve. This is not a plain read: an AI video is stitched from its per-scene clips on demand, and a stored URL that no longer resolves is rebuilt rather than handed back dead, so the call can take a few seconds. A video with no render yet is refused with `warning-source-not-ready`.