{ "componentChunkName": "component---src-templates-markdown-tsx", "path": "/guides/GoToConnect/18_HOW_useMessagingV2Api/", "result": {"data":{"markdownRemark":{"html":"

How to send messages and receive notifications with the Messaging API v2

\n

The GoToConnect Messaging API v2 allows applications to send messages across any type\nof inbox (shared or private) on any supported channel including SMS, WhatsApp, Facebook Messenger, Instagram, Email, and Web Chat.

\n

In this guide, you will learn how to:

\n
    \n
  1. Obtain an access token with the required scopes.
    2. \n
  2. Send messages on each supported channel using ready-to-use curl examples.
    3. \n
  3. Set up a webhook subscription to receive messaging events in real time.
    4. \n
\n

Prerequisites

\n

This article assumes you can make API calls successfully which requires:

\n\n

Authentication Scopes

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ScopeDescription
messaging.v1.sendSend messages through the API
messaging.v1.readRead messages, templates, and attachments
messaging.v1.notifications.manageManage notifications for messages and attachments
\n

When creating your OAuth client or Personal Access Token, ensure at minimum the\nmessaging.v1.send scope is enabled to follow the sending examples below. The\nmessaging.v1.read scope is required for the Retrieving Attachments\nsection. The messaging.v1.notifications.manage scope is required for the\nwebhook notifications section of this guide.

\n
\n

Note: The Messaging API v2 accepts the same scopes as Messaging API v1.\nExisting integrations do not need to re-authorize.

\n
\n

Usage Guidelines

\n

The Messaging API assumes clients are implemented in such a way that unknown attributes are ignored. The addition of new response attributes may occur at any time, for any API response, without prior notice. This is not considered a break in backward-compatibility.

\n

Permissions & Touchpoint Configuration

\n

Before sending messages, ensure the caller has the appropriate permissions for the touchpoint used in the from field:

\n\n
\n

Contact your GoTo account administrator to verify these permissions are in place\nbefore integrating.

\n
\n

Sending Messages

\n

This section provides a copy-pasteable curl example for sending a message on each\nsupported channel. All examples use the\nPOST /accounts/{accountKey}/messages endpoint\nwith multipart/form-data encoding.

\n
\n

Conversation handling: In most cases, you do not need to specify a\nconversationId. The API automatically adds sent messages to an existing open\nconversation between the owner touchpoint and contact touchpoints, or creates a new\nconversation under the inbox where the owner touchpoint is configured.

\n
\n

Replace {ACCESS_TOKEN} with your Bearer token and {accountKey} with your GoTo\naccount key. Your account key can be retrieved via the\nGet Me endpoint.

\n

SMS — Plain Text

\n

Send a simple text message to a single phone number.

\n

Touchpoint format: from and to must be E.164 phone numbers starting with +.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"SMS\",\n    \"from\": \"+15145551111\",\n    \"to\": [\"+15145552222\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Hello from GoTo!\" }\n      }]\n    }]\n  };type=application/json'
\n

SMS — MMS with Attachment

\n

Send a picture message by adding an attachments part. The attachmentName in the\nrequest must match the filename in the form part.

\n

Touchpoint format: Same as SMS plain text — E.164 phone numbers.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"SMS\",\n    \"from\": \"+15145551111\",\n    \"to\": [\"+15145552222\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Check out this photo!\" }\n      }, {\n        \"type\": \"image\",\n        \"attributes\": { \"attachmentName\": \"photo.jpg\" }\n      }]\n    }]\n  };type=application/json' \\\n  -F 'attachments=@photo.jpg;type=image/jpeg'
\n
\n

SMS supports text and attachments combined in a single message. Max total attachment size: 2 MB.

\n
\n

SMS — Group MMS

\n

Send a message to multiple recipients (up to 10) by adding more entries to the to array.

\n

Touchpoint format: E.164 phone numbers.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"SMS\",\n    \"from\": \"+15145551111\",\n    \"to\": [\"+15145552222\", \"+15145553333\", \"+15145554444\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Hey team, meeting at 3pm!\" }\n      }]\n    }]\n  };type=application/json'
\n
\n

SMS is the only channel that supports multiple recipients per message (up to 10).

\n
\n

WhatsApp — Simple Text

\n

Send a plain text message on WhatsApp. If the contact has messaged you within the last\n24 hours, a simple message can be sent. Otherwise, a template message is required (see\nthe WhatsApp Outbound Messaging section of the\nMessaging API v2 reference).

\n

Touchpoint format: from is the numeric Meta WhatsApp phone number ID (not E.164).\nto is the contact's E.164 phone number or BSUID (Business-Scoped User ID).

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"WHATSAPP\",\n    \"from\": \"137169456416846\",\n    \"to\": [\"+15145552222\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Thanks for reaching out! How can I help?\" }\n      }]\n    }]\n  };type=application/json'
\n
\n

WhatsApp does not support text and attachments combined. Send them as separate messages.

\n
\n

WhatsApp — Attachment

\n

Send an attachment message (image, video, audio, or document) on WhatsApp.\nInclude the file as an attachments part and reference it by name in attachmentName.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"WHATSAPP\",\n    \"from\": \"137169456416846\",\n    \"to\": [\"+15145552222\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"image\",\n        \"attributes\": {\n          \"attachmentName\": \"photo.jpg\",\n          \"caption\": \"Check out this image!\"\n        }\n      }]\n    }]\n  };type=application/json' \\\n  -F 'attachments=@photo.jpg;type=image/jpeg'
\n

Web Chat

\n

Send a message to an active web chat session.

\n

Touchpoint format: from is the Widget ID. to is the session identifier.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"WEB_CHAT\",\n    \"from\": \"d4e5f6a7-b8c9-0d1e-2f3a-4b5c6d7e8f90\",\n    \"to\": [\"a1b2c3d4-e5f6-7890-abcd-ef1234567890\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Hello! An agent will be with you shortly.\" }\n      }]\n    }]\n  };type=application/json'
\n

Facebook Messenger

\n

Send a message to a Facebook user who has previously messaged your page.

\n

Touchpoint format: from is your Facebook Page ID. to is the page-scoped user ID.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"FACEBOOK\",\n    \"from\": \"102345678901234\",\n    \"to\": [\"567890123456789\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Thanks for your message! We will get back to you soon.\" }\n      }]\n    }]\n  };type=application/json'
\n
\n

Facebook does not support outbound-first messaging. The contact must have messaged\nyour page first.

\n
\n

Instagram

\n

Send a message to an Instagram user who has previously messaged your page.

\n

Touchpoint format: from is your Instagram Page ID. to is the page-scoped user ID.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"INSTAGRAM\",\n    \"from\": \"17841400123456789\",\n    \"to\": [\"67890123456\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Hi! Thanks for reaching out on Instagram.\" }\n      }]\n    }]\n  };type=application/json'
\n
\n

Instagram does not support outbound-first messaging. The contact must have messaged\nyour page first.

\n
\n

Email

\n

Reply to an existing email conversation. Email requires a conversationId —\nyou can only send messages within an existing conversation.

\n

Touchpoint format: from and to are email addresses.

\n
curl -X POST 'https://api.goto.com/messaging/v2/accounts/{accountKey}/messages' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -F 'request={\n    \"channel\": \"EMAIL\",\n    \"from\": \"support@example.com\",\n    \"to\": [\"customer@example.com\"],\n    \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Thank you for contacting us. Your issue has been resolved.\" }\n      }]\n    }]\n  };type=application/json'
\n
\n

Email does not support outbound-first messaging. A conversation must already exist\nbefore you can send a message. Use the conversationId from the INBOUND_MESSAGE\nwebhook notification that fires when the customer's email arrives (see\nReceiving Events below).

\n
\n
\n

Email supports text and attachments combined in a single message, with no size limits on\nattachments. Add files using the -F 'attachments=@file;type=...' syntax shown in\nthe WhatsApp attachment example above.

\n
\n

Receiving Events with Webhook Notifications

\n

When a subscription is active, the Messaging service delivers real-time events to your\nwebhook as HTTP POST requests. See the\nNotification Channel overview\nfor details on delivery semantics, retry behavior, and channel lifecycle.

\n
\n

Note: While this guide focuses on webhooks, the\nNotification Channel API\nsupports additional channel types. Webhooks are recommended for server-to-server\nintegrations.

\n
\n

All webhook notifications share the following envelope structure:

\n
{\n  \"id\": \"456e7890-e12b-34d5-a678-901234567890\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"INBOUND_MESSAGE\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:30:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": { }\n  }\n}
\n

Where:

\n\n
\n

Consumers should gracefully handle unknown type values. New event types may be added\nwithout prior notice.

\n
\n

Supported Event Types

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Event TypeDescription
INBOUND_MESSAGEA message was received from an external party.
OUTBOUND_MESSAGEA message was sent to an external party.
DELIVERY_STATUSThe delivery status of a sent message changed (e.g. delivered, failed).
INBOUND_REACTIONA reaction was received on a message from an external party.
OUTBOUND_REACTIONA reaction was sent on a message to an external party.
\n

Setting Up Notifications Step by Step

\n

This walkthrough shows how to set up a webhook subscription and receive messaging\nevents end-to-end. Alice is a Super Admin for her organization (accountKey: 9502350087451835131). Her webhook is at https://mycompany.com/sms-webhook.

\n

Step 1 — Create a Notification Channel

\n

Follow the How to create a channel and receiving notifications from GoTo services\nguide to create a webhook channel and obtain a channelId. You will need it in the next step.

\n

Step 2 — Create an Organization Subscription

\n

Using the channelId obtained in Step 1, create a\nsubscription that covers all touchpoints\nin Alice's organization. This only needs to be done once.

\n
\n

Note: This endpoint requires a Super Admin bearer token.

\n
\n
curl -X POST \"https://api.goto.com/messaging/v2/subscriptions\" \\\n  -H \"Content-Type: application/json\" \\\n  -H \"Authorization: Bearer {ACCESS_TOKEN}\" \\\n  -d '{\n    \"accountKey\": \"9502350087451835131\",\n    \"ownerEntity\": \"9502350087451835131\",\n    \"ownerEntityType\": \"ORGANIZATION\",\n    \"channelId\": \"Webhook.cfeb8e9a-495c-4e48-b3bf-fe1b4cf1cf76\",\n    \"eventTypes\": [\"INBOUND_MESSAGE\", \"OUTBOUND_MESSAGE\", \"DELIVERY_STATUS\"]\n  }'
\n

The HTTP 201 Created response confirms the subscription:

\n
{\n  \"id\": \"MTIzNDp4eXo=\",\n  \"ownerEntity\": \"9502350087451835131\",\n  \"ownerEntityType\": \"ORGANIZATION\",\n  \"channelId\": \"Webhook.cfeb8e9a-495c-4e48-b3bf-fe1b4cf1cf76\",\n  \"eventTypes\": [\"INBOUND_MESSAGE\", \"OUTBOUND_MESSAGE\", \"DELIVERY_STATUS\"]\n}
\n
\n

The subscription is bound to the user who created it. If that user is deactivated or\nloses Super Admin privileges, notifications will stop. Re-create the subscription\nwith an active Super Admin if this occurs.

\n
\n

Step 3 — Receive an Inbound SMS

\n

When Bob (+15559998888) sends a message to Alice (+15551234567), the webhook receives\nan HTTP POST with an INBOUND_MESSAGE notification:

\n
{\n  \"id\": \"456e7890-e12b-34d5-a678-901234567890\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"INBOUND_MESSAGE\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:30:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"123e4567-e89b-12d3-a456-426614174000\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"direction\": \"INBOUND\",\n      \"channel\": \"SMS\",\n      \"ownerTouchpoint\": \"+15551234567\",\n      \"contactTouchpoints\": [\"+15559998888\"],\n      \"authorTouchpoint\": \"+15559998888\",\n      \"body\": \"Hello Alice!\",\n      \"attachments\": { \"count\": 0, \"items\": [] },\n      \"timestamp\": \"2025-07-31T10:30:00Z\"\n    }\n  }\n}
\n

Your webhook must respond with an HTTP 2XX (e.g. 204 No Content).

\n

Step 4 — Send an SMS Reply

\n

Alice replies to Bob by sending a message via the API, as shown in the Sending Messages\nsection above:

\n
curl -X POST \"https://api.goto.com/messaging/v2/accounts/9502350087451835131/messages\" \\\n  -H \"Authorization: Bearer {ACCESS_TOKEN}\" \\\n  -F 'request={\n    \"channel\": \"SMS\",\n    \"from\": \"+15551234567\",\n    \"to\": [\"+15559998888\"],\n    \"type\": \"simple\",\n    \"components\": [{\n      \"type\": \"body\",\n      \"components\": [{\n        \"type\": \"text\",\n        \"attributes\": { \"text\": \"Hi Bob!\" }\n      }]\n    }]\n  };type=application/json'
\n

The HTTP 201 Created response confirms the sent message:

\n
{\n  \"id\": \"234f5678-f90a-12b3-c456-536725285111\",\n  \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n  \"accountKey\": \"9502350087451835131\",\n  \"timestamp\": \"2025-07-31T10:31:00Z\",\n  \"channel\": \"SMS\",\n  \"direction\": \"OUTBOUND\",\n  \"from\": \"+15551234567\",\n  \"to\": [\"+15559998888\"],\n  \"body\": \"Hi Bob!\"\n}
\n

If the subscription includes OUTBOUND_MESSAGE, the webhook also receives a notification:

\n
{\n  \"id\": \"789a1234-b56c-78d9-e012-345678901234\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"OUTBOUND_MESSAGE\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:31:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"234f5678-f90a-12b3-c456-536725285111\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"direction\": \"OUTBOUND\",\n      \"channel\": \"SMS\",\n      \"ownerTouchpoint\": \"+15551234567\",\n      \"contactTouchpoints\": [\"+15559998888\"],\n      \"authorTouchpoint\": \"+15551234567\",\n      \"body\": \"Hi Bob!\",\n      \"attachments\": { \"count\": 0, \"items\": [] },\n      \"timestamp\": \"2025-07-31T10:31:00Z\"\n    }\n  }\n}
\n

Step 5 — Receive a Delivery Status Update

\n

Shortly after the outbound message is sent, the webhook receives a DELIVERY_STATUS\nnotification indicating whether the message was successfully delivered or failed:

\n
{\n  \"id\": \"abc12345-d678-90ef-a123-456789012345\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"DELIVERY_STATUS\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:32:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"234f5678-f90a-12b3-c456-536725285111\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"ownerTouchpoint\": \"+15551234567\",\n      \"contactTouchpoint\": \"+15559998888\",\n      \"timestamp\": \"2025-07-31T10:32:00Z\",\n      \"deliveryStatus\": {\n        \"code\": 1000,\n        \"description\": \"DELIVERED\",\n        \"retryable\": false\n      }\n    }\n  }\n}
\n

See the deliveryStatus.code table in the\nSubscriptions API reference for all status codes.

\n

Notification Event Reference

\n

This section documents the payload of each event type delivered to your webhook.

\n

INBOUND_MESSAGE

\n

Delivered when a message is received from an external party. The payload fields use\nownerTouchpoint (the inbox/touchpoint that owns the conversation), contactTouchpoints\n(the external party), and authorTouchpoint (who sent this specific message).

\n
{\n  \"id\": \"456e7890-e12b-34d5-a678-901234567890\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"INBOUND_MESSAGE\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:30:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"123e4567-e89b-12d3-a456-426614174000\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"direction\": \"INBOUND\",\n      \"channel\": \"SMS\",\n      \"ownerTouchpoint\": \"+15551234567\",\n      \"contactTouchpoints\": [\"+15559998888\"],\n      \"authorTouchpoint\": \"+15559998888\",\n      \"body\": \"Hello!\",\n      \"attachments\": { \"count\": 0, \"items\": [] },\n      \"timestamp\": \"2025-07-31T10:30:00Z\"\n    }\n  }\n}
\n

OUTBOUND_MESSAGE

\n

Delivered when a message is sent to an external party. authorTouchpoint is the owner's\ntouchpoint and direction is OUTBOUND.

\n
{\n  \"id\": \"789a1234-b56c-78d9-e012-345678901234\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"OUTBOUND_MESSAGE\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:31:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"234f5678-f90a-12b3-c456-536725285111\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"direction\": \"OUTBOUND\",\n      \"channel\": \"SMS\",\n      \"ownerTouchpoint\": \"+15551234567\",\n      \"contactTouchpoints\": [\"+15559998888\"],\n      \"authorTouchpoint\": \"+15551234567\",\n      \"body\": \"Hi Bob!\",\n      \"attachments\": { \"count\": 0, \"items\": [] },\n      \"timestamp\": \"2025-07-31T10:31:00Z\"\n    }\n  }\n}
\n

DELIVERY_STATUS

\n

Delivered when the delivery status of an outbound message changes (e.g. a failure is\ndetected). See the deliveryStatus.code table in the\nSubscriptions API reference for all status codes.

\n
{\n  \"id\": \"abc12345-d678-90ef-a123-456789012345\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"DELIVERY_STATUS\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:32:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"234f5678-f90a-12b3-c456-536725285111\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"ownerTouchpoint\": \"+15551234567\",\n      \"contactTouchpoint\": \"+15559998888\",\n      \"timestamp\": \"2025-07-31T10:32:00Z\",\n      \"deliveryStatus\": {\n        \"code\": 4000,\n        \"description\": \"INVALID_DESTINATION\",\n        \"retryable\": false\n      }\n    }\n  }\n}
\n

INBOUND_REACTION

\n

Delivered when an external party reacts to a message (e.g. a WhatsApp emoji reaction).

\n
{\n  \"id\": \"bcd23456-e789-01fg-b234-567890123456\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"INBOUND_REACTION\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:33:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"123e4567-e89b-12d3-a456-426614174000\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"emoji\": \"👍\",\n      \"timestamp\": \"2025-07-31T10:33:00Z\"\n    }\n  }\n}
\n

OUTBOUND_REACTION

\n

Delivered when an agent sends a reaction to an external party's message.

\n
{\n  \"id\": \"cde34567-f890-12gh-c345-678901234567\",\n  \"source\": \"inbox-notification\",\n  \"type\": \"OUTBOUND_REACTION\",\n  \"usage\": \"BACKGROUND\",\n  \"timestamp\": \"2025-07-31T10:34:00Z\",\n  \"ttl\": 604800,\n  \"content\": {\n    \"accountKey\": \"9502350087451835131\",\n    \"payload\": {\n      \"messageId\": \"234f5678-f90a-12b3-c456-536725285111\",\n      \"conversationId\": \"987fcdeb-51a2-43d1-b789-123456789abc\",\n      \"emoji\": \"✅\",\n      \"timestamp\": \"2025-07-31T10:34:00Z\"\n    }\n  }\n}
\n

Retrieving Attachments

\n

When an INBOUND_MESSAGE or OUTBOUND_MESSAGE notification includes attachments, the\nattachments field contains metadata for each file:

\n
\"attachments\": {\n  \"count\": 1,\n  \"items\": [\n    {\n      \"name\": \"document.pdf\",\n      \"contentType\": \"application/pdf\",\n      \"size\": 1024000,\n      \"attachmentId\": \"123e4567-e89b-12d3-a456-426614174000\"\n    }\n  ]\n}
\n

To download the file, use the\nGET /accounts/{accountKey}/attachments/{attachmentId}\nendpoint with the attachmentId from the notification. The endpoint returns an\nHTTP 302 redirect to a pre-signed download URL.

\n
\n

Required scope: messaging.v1.read

\n
\n
curl -L -X GET 'https://api.goto.com/messaging/v2/accounts/{accountKey}/attachments/123e4567-e89b-12d3-a456-426614174000' \\\n  -H 'Authorization: Bearer {ACCESS_TOKEN}' \\\n  -o document.pdf
\n
\n

The pre-signed URL expires after 60 seconds. Follow the redirect immediately and do\nnot store the URL for later use. The -L flag tells curl to follow the redirect\nautomatically.

\n
"}},"pageContext":{"slug":"/guides/GoToConnect/18_HOW_useMessagingV2Api/","language":"en"}}, "staticQueryHashes": ["2088588020","2243444437","3138960367","3360603394","943742221"]}