Description/Error
When sending messages to Incoming Webhook part of messages are lost (for example 4 messages in process, I got 3 messages in zoom channel, 1 lost), this error is displayed in the logs:
{“message”:“authorization token valid fail.”,“code”:7010}
Which Endpoint/s or App Types
https://marketplace.zoom.us/apps/eH_dLuquRd-VYcOsNGy-hQ
curl ‘https://inbots.zoom.us/incoming/hook/endpoint ’ -X POST -H ‘Authorization: Verification Token’ -d ‘Hello World!’
tommy
(Tommy Gaessler)
October 31, 2019, 4:51pm
2
Hey @skharitonov , thanks for posting and using Zoom!
I am not sure what the url https://inbots.zoom.us/incoming/hook/endpoint
is.
Are you trying to receive Zoom Webhooks , or send Chatbot/Chat Messages?
Check out these links for instructions on sending a Chatbot message or Chat message .
Also your authorization is incorrect, you need to use an OAuth access_token or Chatbot access_token , not the Verification Token.
Let me know if that helps!
Thanks,
Tommy
Hi @tommy Did you check this link https://marketplace.zoom.us/apps/eH_dLuquRd-VYcOsNGy-hQ ? It’s Incoming Webhook app from marketplace. After installation, I was given endpoint and verification token to send messages to channel.
tommy
(Tommy Gaessler)
October 31, 2019, 6:59pm
5
Apologies @skharitonov , I see now.
What is the curl request you are sending when it fails?
Thanks,
Tommy
curl ‘https://inbots.zoom.us/incoming/hook/1lFG-1c******?format=full ’ -X POST -H ‘Authorization: YkMlVh2KR*******’ -H ‘Content-Type: application/json’ -d ‘{message body}’
The message structure is constant and does not change
message body:
{
"head": {
"text": "Alert Status: FIRING",
"style": {
"color": "#FF0000",
"bold": true,
"italic": false
}
},
"body": [
{
"type": "message",
"text": "Instance: ip:22,Job: SSH",
"style": {
"color": "#666",
"bold": false,
"italic": false
}
},
{
"type": "message",
"text": "[1] 2019-10-28T10:51:09.439Z SSH Critical",
"style": {
"color": "#222222",
"bold": true,
"italic": false
}
},
{
"type": "message",
"text": "Description: ip:22 | TCP: Failed SSH check",
"style": {
"color": "#443333",
"bold": false,
"italic": false
}
},
{
"type": "message",
"text": "Click here to see all alerts",
"link": "http://domain:9093"
},
{
"type": "message",
"text": "Click here to open grafana",
"link": "http://domain:3000"
}
]
}
Hi @skharitonov ,
Can you point out which part of the message gets lost? I tested it and didn’t get an error on my end.
Thanks
Hi @michael_p.zoom
You misunderstood me, I do not lose part of the message (text, links etc). This is a monitoring system and for each warning it sends a message to zoom channel. One warning = one message, so most of the messages I get, but there is a certain percentage of messages that does not reach the channel and in the logs I see this error {“message”:“authorization token valid fail.”,“code”:7010}
tommy
(Tommy Gaessler)
November 6, 2019, 11:15pm
9
Hey @skharitonov ,
Thanks for sharing more details. Can you please provide the accountID and if possible the authorization token so I can look into the logs?
Feel free to private message me them.
Thanks,
Tommy
Hi @tommy
Where can I see the information you requested?
tommy
(Tommy Gaessler)
November 7, 2019, 5:11pm
11
Hey @skharitonov ,
The full verification token sent in the Chatbot message (you shared the screenshot above). No need to send your accountID.
Thanks,
Tommy
@tommy I can’t send a private message, it seems that it is not available for me (or I don’t see where this option is)
tommy
(Tommy Gaessler)
November 7, 2019, 5:48pm
13
Hey @skharitonov ,
I will private message you!
Thanks,
Tommy
tommy
(Tommy Gaessler)
November 19, 2019, 1:51am
14
Hey @skharitonov ,
This bug will be fixed in late December.
Thanks,
Tommy
alon
(Alon)
December 24, 2019, 1:11pm
18
i’m also seeing this issue getting 7010 “authorization token valid error” intermittently.
Any way to track the bug fix ?
tommy
(Tommy Gaessler)
December 26, 2019, 4:41pm
19
Hey @alon ,
You can see my update here on the bug fix:
If you are experiencing an “Invalid Token” error, there is a possibility it is a bug on Zoom’s end. Below are details of the bug, a work around, and when we are releasing a fix:
Conditions: This problem can arise when a token is granted and then
immediately used to call a Zoom API endpoint. The server that issues
the new token sets the nbf (not valid before) time to be the time
“exactly now.” But not all servers at Zoom have synchronized
clocks. If the token is immediately used for an API e…
Thanks,
Tommy
Piggybacking on this:
I’m still struggling to get “participant join” info in Incoming Webhook zoom bot. Sample Curl commands do work. Endpoint URL that incoming webhook bot is created and added to marketplace when webhook app is built. When I add generic webhook website as endpoint URL, join participant does work using https://requestcatcher.com/ Anyone have success to get any event subscriptions to populate in incoming webhook?
tommy
(Tommy Gaessler)
February 25, 2020, 4:58pm
21
Hey @kelly.magaoay ,
Can you get any Zoom webhook working with the incoming webhook chatbot ?
Thanks,
Tommy
So I can get the sample Curl command to post in the zoom incoming webhook chat: