# Retrieving INTEGRATION\_THREAD\_ID

**URL:** <https://community.hubspot.com/t/retrieving-integration-thread-id/150662>\
**Category:** APIs & Integrations\
**Tags:** crm-objects-contacts-companies-deals-tickets\
**Created:** [June 18, 2026, 9:38pm UTC](https://community.hubspot.com/t/retrieving-integration-thread-id/150662 "2026-06-18T21:38:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![humanroach](https://avatars.discourse-cdn.com/v4/letter/h/b5a626/32.png) [@humanroach](https://community.hubspot.com/u/humanroach)\
**Post date:** [June 18, 2026, 9:38pm UTC](https://community.hubspot.com/t/retrieving-integration-thread-id/150662/1 "2026-06-18T21:38:21Z")

</div>

h, if i create a CC message with the INTEGRATION\_THREAD\_ID threading model, is there a way for me to get this integrationThreadId back when i get the message again via API that’s NOT through the webhook event? all i can think of is saving it as a custom property on the message. thanks

---

<div class="post-metadata">

**Author:** ![STierney](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stierney/32/186066_2.png) [@STierney](https://community.hubspot.com/u/STierney)\
**Post date:** [June 19, 2026, 1:16am UTC](https://community.hubspot.com/t/retrieving-integration-thread-id/150662/3 "2026-06-19T01:16:41Z")

</div>

Hey @humanroach,

Thanks for posting in the Community!

I’d like to tag in a few experts here to see what they might recommend!

@zach_threadint, @stefen, and @SteveHTM - do any of you have a workaround here?

Shane, Senior Community Moderator

---

<div class="post-metadata">

**Author:** ![seosiri](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/seosiri/32/10759_2.png) [@seosiri](https://community.hubspot.com/u/seosiri)\
**Post date:** [June 19, 2026, 4:23am UTC](https://community.hubspot.com/t/retrieving-integration-thread-id/150662/4 "2026-06-19T04:23:27Z")

</div>

Hi @humanroach,

Yes, you can absolutely retrieve your original integrationThreadId directly from the message payload without having to listen to the webhook event, and **you do not need the overhead of saving it as a custom property.**

### How it Works Natively:

When you retrieve a message using the Conversations Messages API, HubSpot automatically returns the associated custom channel parameters in the response payload.

Because your channel is configured with the INTEGRATION\_THREAD\_ID threading model, the retrieved message object contains a native property called **channelIntegrationThreadIds** (an array of strings). This array will house the exact external integrationThreadId that was passed when the message was originally created.

### The Endpoints to Use:

To fetch the message history (and get the integrationThreadId in the response), you can use the standard GET endpoints:

- **Get all messages in a thread:**  
GET /conversations/v3/conversations/threads/{threadId}/messages
- **Get a specific message:**  
GET /conversations/v3/conversations/threads/{threadId}/messages/{messageId}

### Example Response Payload:

When you perform the GET request, the returned JSON will contain the thread mappings like this:

codeJSON

```auto
{
  "id": "message_id_here",
  "threadId": "hubspot_thread_id_here",
  "channelId": "your_custom_channel_id",
  "channelIntegrationThreadIds": [
    "your_original_external_integration_thread_id"
  ],
  "type": "MESSAGE",
  "text": "Hello, this is the message content..."
  // ... other standard message fields
}

```

This completely eliminates the need for custom property syncing!

### Official HubSpot Developer Resources:

- **Custom Channels API Guide:** You can review the full details on how different threading models return these properties in the **[Custom Channels API Guide](https://developers.hubspot.com/docs/api-reference/legacy/conversations/custom-channels/guide)**.
- **Conversations Messages Endpoint Reference:** See the exact message schemas and returned fields in the **[Retrieve Messages API Reference](https://developers.hubspot.com/docs/api-reference/latest/overview)**.

Let me know if this helps resolve your custom channel threading workflow!

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [June 26, 2026, 2:16am UTC](https://community.hubspot.com/t/retrieving-integration-thread-id/150662/5 "2026-06-26T02:16:00Z")

</div>

Automatically bumped on June 26, 2026, 2:16am UTC