Once Fin has returned a response to a user's message, its status will be awaiting_user_reply.
If a user replies, use this endpoint to send this response to Fin.
To request access to the Fin Agent API, please fill out this form.
Intercom API version.
By default, it's equal to the version set in the app package.
An array of attachments to include with the message. Maximum of 10 attachments.
- The production API serverhttps://api.intercom.io/fin/reply
- The european API serverhttps://api.eu.intercom.io/fin/reply
- The australian API serverhttps://api.au.intercom.io/fin/reply
- Basic reply
- Reply with attachments
curl -i -X POST \
https://api.intercom.io/fin/reply \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Intercom-Version: 2.14' \
-d '{
"conversation_id": "123456",
"message": {
"author": "user",
"body": "Here'\''s the information you requested.",
"timestamp": "2025-01-24T09:01:00.000Z"
},
"user": {
"id": "123456",
"name": "John Doe",
"email": "john.doe@example.com"
}
}'Reply sent successfully
Fin's current status in the conversation workflow.
The timestamp the response was created at, with millisecond precision.
Contains error details if any user or conversation attribute updates failed.
Optional. A URL to subscribe to Server-Sent Events (SSE) for this conversation, if SSE is enabled. The access token is a JWT with a 3-minute TTL. The token is revoked when Fin sets the conversation to awaiting_user_reply or complete status. When CSAT is enabled and a survey will follow the resolution, complete revocation is deferred until the csat_requested event is delivered or the token expires.
- Successful response
- Response with attribute errors
{ "conversation_id": "ext-123", "user_id": "user-456", "status": "thinking", "created_at_ms": "2025-01-24T10:00:00.123Z", "sse_subscription_url": "https://primary-realtime.intercom-messenger.com/event-stream?channels=fin_agent_api:app123:ext-123&accessToken=eyJhbG..." }