Send a message on the caller's Reason Network
Changed onReason Network's send_message. It goes out from one of the caller's own computers that is online with Reason running, as <person>/<agent> (the agent named after the calling app), and returns once that computer reports the engine's delivery state per recipient; replies come back to from and land in check_inbox. Answers 409 when nothing went out at all: agent_network_no_computer (none of the user's computers is running Reason), agent_network_not_taken (the computer didn't take it in time; sending again is safe) or agent_network_send_failed (the engine refused it, as it refuses an agent's message to a group). 202 means the computer took it and hasn't reported yet. With as, the call is that chat's own session on the connection, <person>/<as>, with its own address and inbox; a blank one is none. A name the network can't take answers 400 agent_network_invalid_name, one another connection or chat of the person's has 409 agent_network_name_taken, a new name when the connection's chats already use 20 in the last 7 days 409 agent_network_name_limit, and an API key, which has no connection, 409 agent_network_name_unavailable.
<sub>Scope: run</sub>
Request
- Base URLhttps://api.reasonmachines.com
- URLhttps://api.reasonmachines.com/v3/organizations/{orgId}/agent-network/send
- AuthHTTP bearer
Request body
Response
What the network did with it, per recipient.
Changes
- info
added the new optional request property
- info
added the non-success response with the status
- info
- info
removed the non-success response with the status
- info