Submit an inbound message
Submit a message written by one of your users and let the Shortext agent answer it.
Reply modes
sync: the request waits for the agent reply (max ~25 s) and returns it inbody.replies. On timeoutbody.statusispendingand the reply is delivered to your webhook.async: the request returns immediately withaccepted; replies are delivered to your webhook.
Idempotency: message.id is your own message id. Sending the same id again returns
duplicate with the original message, without a second reply.
Webhook: replies (async, sync timeout, human agent answers) are POSTed to the endpoint
webhook as message.sent events (ShortextWebhookEvent body), signed with
X-Shortext-Signature: sha256=hex(hmac_sha256(secret, "{X-Shortext-Timestamp}.{raw_body}")).
Retried for ~21 h on failure; dedupe on the event id.
Autorisations
Company API key, sent as Authorization: Bearer <key>. Create it in the dashboard (Developer > API Keys) with the permissions the integration needs.
Corps
Only native channels accept inbound messages
shortext "shortext"
Endpoint ID shown in the Shortext dashboard
"ste_8k2m4q9x1v7c3n5b6z0p2r4t"
Defaults to the endpoint setting
sync, async "sync"
Réponse
Message stored. See body.status for the reply outcome.
Envelope of every response (always HTTP 200): only body changes from one endpoint to another.
true
Standard response codes defined by the system / Codes de réponse standard définis par le système.
-1, -2, -3, -4, -5, 1000, -1001, -1002, -1003, -1004, -1005, -1006, -1007, -1008, -1009, -1010, -1100, -1101, -1102, -1103, 1104, -1105 1000
"Request success"
Endpoint-specific payload, null on most errors
Present only on authentication routes
Present only when success=false. Give it to support.