get_status for a quote, with a message to the operator
This is get_status with the optional message, as a POST so that the text is in the body, not in the URL (which servers log). Without a message (empty body, or {"message": null}) it is a plain status call, like the GET. With a message it is written to the thread and e-mailed to the operator, and the answer is the same as the GET's, including your message (from: agent) and message_sent: true. Read the operator's message first, then reply: while the operator has written something you have not read yet, nothing is stored or e-mailed; the answer is the GET's, with that message in messages, message_sent: false and a next_action that says so, and you send your answer with the next call (HTTP 200 either way, so check message_sent). Plain text, 1-2000 characters, never interpreted as HTML; an empty or longer message is a 400. Limits: 10 messages per hour per quote (its quote_id and task_id share it) and 30 per hour per client address (429). The same text again within 10 minutes, while it is still the newest message of the thread, is not stored or e-mailed a second time (the answer then has duplicate_ignored: true). It needs the same access_token as the GET; without one, or with another quote's, nothing is stored or sent (401).
Request
- Base URL: https://api.handsforagents.com/v1
- URL: https://api.handsforagents.com/v1/quotes/{quote_id}
- Auth: HTTP bearer
Path parameters
Request body
Response
The same answer as the GET, now including your message; if the operator had written something you had not read, message_sent is false, nothing was stored and the answer shows that message
Changes
No recorded changes to this operation across all 1 revision of this API.