create_from_batches is an alias of create_from_batch: passing the same list
to either makes the same creation request. A folder-based Studio uses the
folder’s videos and eligible completed analyses already associated with them;
it does not analyze footage again. In the app, owners can add eligible batches
to an existing Studio. The SDK currently has no studio.add_batch() helper.
Create from a batch
Use an API key with write access and a completed batch you can access:batch returned by the
Structured Output example:
Each creation call creates a new Studio. These examples are alternatives, not
steps.
Create from multiple batches
studio["buckets"] and compare its
sub_batch_id and query_label entries with the parent’s child queries. A
partially successful parent can therefore produce fewer buckets than queries.
Create from folders
Creation is not search readiness
create_from_batch() returns the Studio record and studio.url as soon as
creation succeeds. Search indexing may still be starting or building. The SDK
does not expose one universal studio.ready state: Deep Search
waits and reports index status when needed, while taxonomy runs
have their own run.wait() lifecycle. A search timeout means the index was not
ready within that wait; it does not undo Studio creation. Retry the search
later, and check taxonomy schema or facet availability separately before
relying on filters.
The Studio object
Every creation call returns aStudioDataset:
StudioDataset is also a dictionary, so the full API response is available by
key, for example studio["buckets"]. Batches can contain several events from
the same video. video_count deduplicates video IDs; event-level queries and
exports use event IDs and may return several events per video.
Retrieve Studios
get() fetches fresh detail for one Studio. list() returns the Studios you
own.
Next: Search your Studio or
add taxonomies.