The studio, headless

Same studio, headless.

Every tool in the console has an endpoint behind it. Keep the studio for your team, and run the volume from your own backend.

01

Console for people, API for volume

Editors and producers work in the studio. The nightly batch of two hundred episodes runs through the API. Same models, same quality, different front door.

02

Scoped keys, per project

Issue keys scoped to what each integration needs, so a transcription pipeline holds transcription access and nothing else. Keys carry allowed-origin lists and expiry dates, and live inside the project they belong to.

03

The same pipeline, in code

Transcribe, synthesise, isolate, and generate documents programmatically. Anything the studio does by hand, your backend can do on a schedule.

Full API reference in the developer docs

→

More from the studio

Partner ecosystem

Trusted Across the
Technology Ecosystem

Hamsa works with leading technology companies, integrators, and solution providers to bring enterprise Voice AI to organizations across the region.