Queue a reply to an existing conversation
Requires conversations:write and Idempotency-Key. At least one of text, mediaId or media is required; media and mediaId are mutually exclusive. URL attachments are available by default and supported on WhatsApp, Instagram and Messenger according to channel capabilities; webchat is not supported. 202 means queued, including preparation, not delivered. M2M has no multipart upload endpoint. Replies inherit the business reply-pause preference (normally 30 minutes). Optional autoFreeze mode pause with minutes 1-120 overrides it; mode off preserves existing pauses. Application is asynchronous after acceptance, without waiting for preparation or delivery. Replays retain the original choice and timer. Read frozenUntilAt or GET policy for expiry; PATCH policy with unfreeze:true clears the timer.
Authorizations
Server-side tenant-scoped credential created from Build > API Keys.
Headers
Stable key for one intended outbound operation. Reuse it only with an identical request.
1Path Parameters
Body
- Option 1
- Option 2
- Option 3
4096Existing Visito media asset for this conversation. Mutually exclusive with media.
One remote attachment, available by default. Unsupported channel combinations are rejected without falling back to a text link. Visito downloads and stores the file asynchronously.
- Option 1
- Option 2
Omit to inherit the business default. Off preserves an existing pause. Mode is recommended; enabled is retained only for legacy compatibility.
- Option 1
- Option 2
- Option 3
- Option 4