DubSync for developers
Your workflow.
More languages.
Bring video translation into the tools you already use. One account, one media workflow, and the same allowance across the app, API, and connected assistants.
01 / REST API
From upload to translated video
Upload source media, get a quote, create a translation, and retrieve the result. Resumable uploads and request identities let your integration recover from interruptions.
curl "$DUBSYNC_ORIGIN/api/public/v1/projects" \
-H "Authorization: Bearer $DUBSYNC_API_KEY"02 / MCP
A connection for your assistant
Connect an MCP client to /mcp with OAuth. Discover languages, inspect your projects, review usage, and request a translation with your approval.
Import supported ChatGPT video attachments up to 128 MiB with your permission, or use the resumable API for larger files. Translation requires a separate approval.
Connection details ↓A predictable translation workflow
- Create a scoped key. Start with account and project read access. Add upload and project write permissions when your workflow needs them.
- Upload your source. Create an upload at
POST /api/public/v1/uploads, send its bytes with resumable PATCH requests, then complete it. - Review the quote. Choose a target language and request a quote. The server determines media duration and available allowance.
- Start with approval. Confirm media rights and authorize the requested translation. Reuse the same idempotency key when retrying the same request.
- Follow progress and download. Read the project status and fetch its result when ready. Download links expire; retrieve a fresh result when needed.
Connect over MCP
- Endpoint
https://dubsync.me/mcp- Transport
- Streamable HTTP, stateless JSON responses
- Authorization
- OAuth authorization code with PKCE (S256)
- Discovery
- Protected resource metadata
In a compatible ChatGPT workspace, add a custom MCP server and select OAuth with dynamic client registration. Client availability and workspace policies apply. A custom connection does not imply directory approval.
Access you can control
Keys have explicit permissions and expiry. Connected apps ask for consent. You can revoke either from Developer settings.
The API uses your existing account credits and eligible free allowance. It cannot purchase credits or change a subscription.
Build from the contract
The OpenAPI document includes authentication, scopes, request bodies, upload headers, and error responses. Use the deployment’s own origin for API and OAuth endpoints.