# Cannot update message status

**URL:** <https://community.hubspot.com/t/cannot-update-message-status/147667>\
**Category:** APIs & Integrations\
**Tags:** timeline-and-extensions-apis\
**Created:** [March 25, 2026, 2:22pm UTC](https://community.hubspot.com/t/cannot-update-message-status/147667 "2026-03-25T14:22:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lswiatek](https://avatars.discourse-cdn.com/v4/letter/l/7ab992/32.png) [@lswiatek](https://community.hubspot.com/u/lswiatek)\
**Post date:** [March 25, 2026, 2:22pm UTC](https://community.hubspot.com/t/cannot-update-message-status/147667/1 "2026-03-25T14:22:37Z")

</div>

Hello,

I’m integrating a custom message channel to be used in Help Desk. According to the docs, there’s an endpoint for updating the message status to READ or FAILED:

> **[Accounts Dashboard | HubSpot](https://app.hubspot.com/myaccounts?next=developerdocs&redirect=%2Fapi-reference%2Fconversations-custom-channels-v3%2Fexternal-messages%2Fpatch-conversations-v3-custom-channels-channelId-messages-messageId)**

However, when I try to use it I get 403 response with message: “message”: “There was a problem with the request.”.  
I tried both updating the status to READ or FAILED with or without errorMessage. I’m sure I’m using the correct token with appropriate scopes and correct channelId and messageId.  
Am I missing some configuration?  
Best regards

Lucas

---

<div class="post-metadata">

**Author:** ![stassey](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stassey/32/36_2.png) [@stassey](https://community.hubspot.com/u/stassey)\
**Post date:** [March 25, 2026, 4:35pm UTC](https://community.hubspot.com/t/cannot-update-message-status/147667/2 "2026-03-25T16:35:35Z")

</div>

Hello @lswiatek,

Welcome to the Community!

I wasn’t able to find anything quite like this already in the community. With that in mind, I’d like to tag in some of our Top Contributors to see if they have any expert insight they can share here!

@SteveHTM, @Josh, @RubenBurdin-- Do you have any suggestions for @lswiatek on this 403 error they’re receiving?

Thanks!

Sam, Community Manager