Sales order messages
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/sales-order-messages.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
The conversation with the customer on an order: its participants and the emails and text messages sent to them.
5 operations
- POSTAdd a participant to an order
/Participants are the people who can receive an order's messages: contacts of the customer, or guests with just an email address.v1/ api/ store/ {team_slug}/ sales_order/ {hash_id}/ participant - GETList the messages of an order
/Returns the conversation with the customer on a sales order or quote, oldest first, with each message's attachments.v2/ api/ store/ {team_slug}/ v2/ sales_order/ {hash_id}/ message - GETList the participants of an order
/Participants are the people who can receive an order's messages: contacts of the customer, or guests with just an email address.v1/ api/ store/ {team_slug}/ sales_order/ {hash_id}/ participant - POSTSend a message to the customer
/Sends a message about a published sales order or quote to its participants, by email or text message, and saves it in the order's conversation.v2/ api/ store/ {team_slug}/ v2/ sales_order/ {hash_id}/ message - PATCHRemove every participant from an order
/Removes all participants of a sales order.v1/ api/ store/ {team_slug}/ sales_order/ {hash_id}/ participant/ clear
Legacy and internal (2)
Prefer the operations above. Legacy operations name their replacement; internal ones are built for YoPrint's own apps.
- GETList the messages of an order (v1)Legacy · deprecated
/Returns the same conversation as the v2 list.v1/ api/ store/ {team_slug}/ sales_order/ {hash_id}/ message - POSTSend a message to the customer (v1)Legacy · deprecated
/Sends a message like the v2 operation, with the same body, but it also accepts drafts.v1/ api/ store/ {team_slug}/ sales_order/ {hash_id}/ message
