Skip to main content
POST
/
v1
/
inbox
/
messages
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"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
x-api-key
string
header
required

Body

application/json
​
contactId
integer
required

Contact ID to reply to

Example:

123

​
senderIdentityId
integer
required

Sender identity ID that owns the conversation

Example:

14

​
message
string
required

Reply message content

Minimum string length: 1
Example:

"Absolutely. I just sent over our pricing breakdown and can walk through it live if helpful."

​
type
enum<string>

Optional channel to use when selecting the matching conversation. Defaults to the last replyable message channel

Available options:
EMAIL,
LINKEDIN
Example:

"EMAIL"

​
attachment
object

Optional single attachment supported by the manual reply flow

​
requestId
string

Optional idempotency key suffix for the manual reply

Minimum string length: 1
Example:

"manual-reply-20260320-001"

Response

Inbox message sent successfully

​
status
enum<string>
required
Available options:
success
​
message
string
required
​
data
object
required