Async tasks & webhooks: the right way to scale

All generation tasks are asynchronous. A successful request returns HTTP 200 and a task_id — the task is created, not completed.

To get results, either provide a webhook URL and receive a push when the task finishes, or poll the query-record-info endpoint with the task_id.

For production traffic, webhooks are usually cheaper and lower-latency than tight polling loops, and they scale better under concurrency.

← Back to blog