Skip to main content

Documentation blur: bearer token in async action block result report

  • February 25, 2026
  • 1 reply
  • 8 views

Hello,

In order to report an action block result, the documentation mentions:

“This JWT is then sent in the Authorization header as a Bearer token. It should include your appId in the payload.”

While the example shows no mention of “Bearer”:

# The `callbackUrl` received from monday in the initial POST request body
POST https://callback-to-monday.com/callbacks/12345678 HTTP/1.1
Content-Type: application/json
Authorization: <SIGNED_JWT_TOKEN>

The example is the way to go. A token sent as Bearer will not work.

Thank you,

1 reply

rachelatmonday
Forum|alt.badge.img
  • monday.com Team Member
  • February 25, 2026

Hi ​@hasen74

 

Thanks for letting us know! The documentation has been updated. 

 

Best, 
Rachel