curl --request POST \
--url https://openapi.enginy.ai/v1/inbox/messages \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"contactId": 123,
"senderIdentityId": 14,
"type": "EMAIL",
"message": "Absolutely. I just sent over our pricing breakdown and can walk through it live if helpful.",
"requestId": "manual-reply-20260320-001"
}
'{
"status": "success",
"message": "Inbox message sent successfully",
"data": {
"contactId": 123,
"conversationId": 456,
"type": "EMAIL",
"success": true,
"message": "Message queued successfully"
}
}Send inbox message
Send a manual inbox reply through Enginy conversation routing.
Required body fields:
- contactId: contact whose thread should receive the reply.
- senderIdentityId: sender identity that owns the target thread.
- message: plain-text body of the manual reply.
Optional body fields:
- type: channel used to select the matching conversation. Allowed values are EMAIL and LINKEDIN. If omitted, Enginy falls back to the latest replyable message channel on the matched thread.
- attachment: one attachment with url, name, and MIME type, supported only when the selected channel is LINKEDIN.
- requestId: idempotency suffix for safely retrying the same manual reply.
EMAIL does not support attachment. Host the file yourself and include its URL in message. An attachment on a selected EMAIL thread returns 400 and rejects the entire request, including the text body. This also applies when type is omitted and EMAIL is selected automatically.
Required scope:
MESSAGING_WRITERate limit: 30 requests per minute
curl --request POST \
--url https://openapi.enginy.ai/v1/inbox/messages \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"contactId": 123,
"senderIdentityId": 14,
"type": "EMAIL",
"message": "Absolutely. I just sent over our pricing breakdown and can walk through it live if helpful.",
"requestId": "manual-reply-20260320-001"
}
'{
"status": "success",
"message": "Inbox message sent successfully",
"data": {
"contactId": 123,
"conversationId": 456,
"type": "EMAIL",
"success": true,
"message": "Message queued successfully"
}
}Authorizations
Body
Contact ID to reply to
123
Sender identity ID that owns the conversation
14
Reply message content. For EMAIL file sharing, include a caller-hosted file URL in the body.
1"Absolutely. I just sent over our pricing breakdown and can walk through it live if helpful."
Optional channel to use when selecting the matching conversation. Defaults to the last replyable message channel
EMAIL, LINKEDIN "LINKEDIN"
Optional single attachment, supported only when the selected channel is LINKEDIN. EMAIL attachments return 400, including when type is omitted. Host EMAIL files yourself and include their URLs in message instead.
Show child attributes
Show child attributes
Optional idempotency key suffix for the manual reply
1"manual-reply-20260320-001"