Skip to content

Set a message's status

Open .md

PUT/v2/api/store/{team_slug}/messages/{hash_id}/status

v2Operation ID v2_public_messages_status

Sets your team's own status on a message, such as "Need to Respond" or "Completed", for sorting your inbox. It does not change delivery and does not notify the customer.

Use a status id from your team's message statuses (GET /v1/api/store/{team_slug}/setting/status/customer_message). Returns the message with previous_status_id and previous_message_status.

Permission

Any member can read purchase order messages. For sales order and quote messages you need permission to message all orders, or only the orders you created or are assigned to. The team owner sees everything.

Business rules

  • status_id is required and must be one of your team's statuses. Use a message status: other kinds of status are accepted too, but they are not meant for messages.

Side effects

  • Fires the message.status_changed webhook, every time, even if the status was already set to this value.
  • Records the change in the status history when the message had a different status before.
  • People with the inbox open see the change live.

Path parameters

  • team_slugstringrequired

    Your team slug, shown as Team ID next to your API key in Profile.

    • Example your-team
  • hash_idstringrequired

    The message's id, from the message list. A hash id; unique keys and document numbers are refused with 404.

    • Example u7HKhdhT6tkEUy

Request body

application/json, required.

  • status_idstringrequired

    One of your team's message status ids.

  • Accepted but ignored: no notification is sent.

Response

200Successful response.

  • dataobjectrequired
    Child fields (37)
    • actor_namestring | null

      The writer's name, by actor_type: your team's name for system, the team member, the contact, the order's customer, the purchase order's vendor, the participant, or the name a guest gave. Null when YoPrint can't find the writer's record.

    • Who wrote it: user, customer, vendor, contact (written in the customer or vendor portal), participant, guest (someone who is not a contact) or system.

    • attachmentsarray of objects

      Files attached to it, in the same shape as an upload (id, name, file_name, mime_type, size, url).

    • contactobject | null

      The contact who wrote it, when contact_id is set: first_name, last_name, email, phone and more.

    • contact_idstring | null
    • created_atstring (date-time)
    • delivery_summaryobject | null

      Outbound messages: how delivery went across all recipients. Null for inbound messages.

      Child fields (12)
      • acceptedinteger
      • completeboolean
      • deliveredinteger
      • failedinteger
      • reasonstring | null

        Why the state is not final, or why nothing was sent, for example no_recipients or delivery_evidence_unavailable. Usually null.

      • retryableboolean

        True when the retry operation accepts this message. When false, it answers 422.

      • skippedinteger
      • statestring

        sent: the provider took it, delivery not confirmed yet. partial: recipients are in different states. not_sent: there were no recipients.

        • One of: "pending", "sending", "sent", "delivered", "failed", "partial", "unknown", "not_sent"
      • submittinginteger
      • totalinteger
      • unknowninteger
      • waitinginteger
    • How the web app draws it, for example default_v2, or system_v2 for automatic messages.

    • driverstring | null

      email, sms, or web for a message written in YoPrint.

    • emailstring | null

      The sender's email address.

    • idstring
    • messagestring | null

      The message as it was written, without the email layout.

    • The author, as a message participant.

    • message_statusobject | null

      The status named by status_id: id, role (customer_message), type, label, customer_label, color, position, trashed.

    • namestring | null

      The sender's name.

    • order_idstring | null

      The sales order or quote it is on.

    • order_object_typestring | null

      sales_order or quote. Null without an order.

    • order_quoteboolean | null
    • order_scoped_idstring | null

      The order's number, such as SO1001. An empty string "" (not null) without an order.

    • original_messagestring | null

      The whole message as HTML: for a reply, the email as it arrived, with any quoted text; for a message you sent, the full message YoPrint rendered.

    • participantobject | null

      The author, as a message participant, when message_participant_id is set. Its delivery_* fields are null.

      Child fields (24)
    • preview_messagestring | null

      A short plain-text preview.

    • That status, in the same shape as message_status: id, role, type, label, customer_label, color, position, trashed.

    • previous_status_idstring | null

      The status before this change. Null when none was set.

    • purchase_order_idstring | null

      The purchase order it is on.

    • purchase_scoped_idstring | null

      The purchase order's number. Null when it is not on a purchase order.

    • recipientsarray of objects

      Who it was sent to: each participant with its delivery (delivery_status, delivery_channel, delivery_destination). delivery_id is the id the recipient operations take.

      Fields of each item (24)
    • rendered_attachmentsarray of objects

      Everything attached when it was sent: the files (attachment_type media, upload shape) and generated documents such as the order PDF (attachment_type internal_attachment, with name and url).

    • retryableboolean

      For outbound messages, the same as delivery_summary.retryable.

    • statusstring | null

      Older delivery status word, such as pending, dispatched, partial_delivered, delivery_failed, delivered, or received for a reply. Prefer delivery_summary.

    • status_idstring | null

      Your team's message status (for example "Needs reply"), set with the status operation. Null when none is set.

    • systemboolean

      True for messages YoPrint sent automatically.

    • typestring

      outbound: sent by your team. inbound: a reply received.

      • One of: "outbound", "inbound"
    • userobject | null

      The team member who wrote it, when user_id is set.

      Child fields (5)
    • user_idstring | null
  • statusintegerrequired
  • successbooleanrequired

Errors

  • 401The API key is missing or wrong (unauthenticated).

  • 403You are not allowed to do this. api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only {"message": "Insufficient Permission"}. Other refusals use the error envelope, with unauthorized or user_is_not_authorized.

    When
    The message is on a sales order or quote you can't message (user_is_not_authorized).
    Fix
    Ask a team admin for permission to message that order.
  • 404Not found. page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. code: null, with a message that starts "No query results for": there is no record with that id.

    When
    The message or the status does not exist on this team.
    Fix
    Use ids from the API.
  • 422The request was refused and changed nothing. validation_failed lists what to fix in error.fields; other codes name a business rule, explained in error.message. A few checks answer with only {"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer connect_timeout ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.

    When
    status_id is missing or not an id, or notify_customer is not a boolean (validation_failed; error.fields names the field).
    Fix
    Send a status id.