Start an asynchronous chat request and return a job ID for polling.
Use this for long-running document operations. The request is processed in the background. Poll the job status using GET /v1/jobs/ until status is ‘completed’ or ‘failed’. The result contains the AI response and any document changes, same as the sync chat endpoint.
Optional parameters:
HITL workflow (approval_mode=‘ask_every_time’):
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Start an async chat request that processes in the background.
Your message to the AI assistant.
Unique session identifier. Reuse to continue a conversation.
Current document HTML. Include data-chunk-id attributes on elements to enable targeted AI edits.
User identifier. Automatically set from authentication — typically omit this.
Inline images for vision-based analysis (base64-encoded).
Must be true for async processing. Included for backward compatibility.
AI model to use: 'core' (default, fast), 'turbo' (fastest), 'pro' (advanced reasoning), 'max' (most capable).
Reasoning depth: 'fast', 'balanced' (default), or 'deep'. Controls how much analysis the AI performs.
Change review mode: 'approve_all' (default, auto-applies changes) or 'ask_every_time' (pauses for your review).
Successful Response
Response from starting an async chat request.