API & integrations

Disclaimer:
This FAQ provides general information about Rask AI’s Enterprise features and services. It does not form part of any agreement or establish standard contractual terms or commitments. Features, service levels, data processing and retention arrangements and other service commitments are governed by the applicable Terms of Service, Order Form, Data Processing Agreement and any other agreement between the parties. If this FAQ differs from those documents, those documents control. Please contact our team to confirm any specific requirements in writing.

Is there an API, and what can it do?

Yes. The Rask API v2 covers media upload (file or link), transcription from your own segments or SRT files, project creation and dubbing, speakers and voices, glossaries, redubbing after edits, lip-sync and credit balance.
Authentication uses OAuth 2.0 client credentials. An official Python SDK (Python 3.8+) is available. Documentation: https://docs.api.rask.ai/introduction

What does a typical API workflow look like?

1) Upload your file or a link.

2) Optionally create a transcription from your own SRT file or segments.

3) Create the project.

4) Check the project status and download the artifacts from the links provided.

5) Optionally run lip-sync. After editing segments, voices or translation, you can regenerate the dub without uploading the media again.

Can Rask be deployed on-premise or in our own cloud?

In certain cases, it can be delivered as a custom solution for Enterprise clients. Contact your account manager to discuss your requirements.

Do you work with resellers and system integrators?

Yes. Contact your account manager to discuss the details.