H3 Max API Guide
Connect an application to H3 Max generation while keeping credentials server-side and handling long-running video jobs asynchronously.
Choose the endpoint by input type
Turbo provides text-to-video and image-to-video routes. H3 Max provides text-to-video, image-to-video, and reference-to-video. Validate required fields and supported controls against the exact route instead of sending one generic payload everywhere.
Keep API keys on the server
Create and revoke keys from the signed-in account area. Store keys in server-side secrets, scope access where possible, rotate exposed credentials immediately, and never embed a secret in browser JavaScript or a public repository.
Design for asynchronous completion
Video generation is not an instant request-response workflow. Record the returned task identifier, poll or process status updates safely, handle timeouts without duplicating paid submissions, and persist the completed output your application needs.
Handle credits and failures explicitly
Estimate the selected model, duration, resolution, and reference-token cost before submission. Track reservation and settlement records, use idempotent application logic, and surface actionable errors without exposing provider credentials or internal responses.
Questions
Frequently asked questions
Can I call H3 Max directly from browser code?
Do not expose a secret API key in browser code. Send authenticated requests through your own server or another protected backend.
Are video requests synchronous?
No. Treat generation as an asynchronous task and store its identifier so status and settlement can be reconciled.
Where do I manage API keys?
Signed-in users manage keys from the account API area. The public page explains integration concepts without exposing account controls.