Connect video work to your product.
Evaluate a server-side integration around media, task state and available deliverables. Keep credentials out of the browser.
A candidate API, not a stability promise
The candidate public API covers media, uploads, tasks, results, batches, glossaries, usage and related project controls. An endpoint in the contract does not automatically mean a processing route is enabled.
Agree the environment, identity, project scope and supported workflow before integrating. This is not a stable public-release or production-readiness commitment.
What the Web console exposes
Review project-scoped service accounts and existing API-key metadata. Authorized administrators can create or suspend service accounts and revoke existing key metadata.
Web key issuance is disabled. API-key secrets must not enter the browser. Webhook management is not exposed by the current Web console; server-side evaluation must follow the approved API route and release scope.
SDK availability
The private Python and TypeScript SDK candidates are not published. These candidate packages are private; there is no public SDK download or installation promise on this site.
Define the first integration
- Confirm which ready-media and task routes the environment supports.
- Use an authorized server-side identity and project scope.
- Follow service-owned state, retries and result availability.
- Handle partial failure and expired transfer capabilities explicitly.