Error with a newly generated token

Hello

I’ve been having problems lately with the automatic closure of a session.
The script runs smoothly, but there are a few calls that generate errors with the API: https://api.zoom.us/v2/meetings/meeting_id/status
The log below shows the generation of a token and its use a few milliseconds later.

2023-12-11 15:00:07,391 INFO:HTTP Request: POST https://zoom.us/oauth/token?grant_type=account_credentials&account_id=SPsqoxwjTpqO-SLhtl30rw "HTTP/1.1 200 OK"
2023-12-11 15:00:07,392 INFO:New Token: Bearer eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6ImQyOWViYjc4LTdmNGMtNDIzNC04NGI0LTI5MmViYTBlZjRiZSJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFYWpTZGdPcVJVT0RzN1JHUVFZVTN3IiwidmVyIjo5LCJhdWlkIjoiY2M3Y2JhZTQ1MzY4MGYzYTdiZmUyNjAyZDU2NGQ0MzUiLCJuYmYiOjE3MDIzMDMyMDcsImNvZGUiOiJiMUN3NXdWSVFGaXVfdWR3YjRtZ2tnRUNyMmJhSTZLU1EiLCJpc3MiOiJ6bTpjaWQ6Y2duNUN0aHZTX2FXdW5YQ0ZoQk9zZyIsImdubyI6MCwiZXhwIjoxNzAyMzA2ODA3LCJ0eXBlIjozLCJpYXQiOjE3MDIzMDMyMDcsImFpZCI6IlNQc3FveHdqVHBxTy1TTGh0bDMwcncifQ.Ve49nYm4VnyhhYXMkgIE1AfeKCshY_8hdjVQgEXCnUJDL8q3hDT2cqapFkQhqFJ2z0zeyiVd8P2JTgIZd8Wv8w
2023-12-11 15:00:07,392 INFO:ClientId : cgn5CthvS_aWunXCFhBOsg
2023-12-11 15:00:07,397 INFO:PUT:https://api.zoom.us/v2/meetings/82322546443/status
2023-12-11 15:00:12,420 ERROR:Error : 
2023-12-11 15:00:12,420 ERROR:Headers Error : https://api.zoom.us/v2/meetings/82322546443/status
2023-12-11 15:00:12,421 ERROR:Client Header : Headers({'accept': '*/*', 'accept-encoding': 'gzip, deflate', 'connection': 'keep-alive', 'user-agent': 'python-httpx/0.24.0', 'authorization': '[secure]', 'content-type': 'application/json'})
2023-12-11 15:00:12,421 ERROR:authorization : Bearer eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6ImQyOWViYjc4LTdmNGMtNDIzNC04NGI0LTI5MmViYTBlZjRiZSJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFYWpTZGdPcVJVT0RzN1JHUVFZVTN3IiwidmVyIjo5LCJhdWlkIjoiY2M3Y2JhZTQ1MzY4MGYzYTdiZmUyNjAyZDU2NGQ0MzUiLCJuYmYiOjE3MDIzMDMyMDcsImNvZGUiOiJiMUN3NXdWSVFGaXVfdWR3YjRtZ2tnRUNyMmJhSTZLU1EiLCJpc3MiOiJ6bTpjaWQ6Y2duNUN0aHZTX2FXdW5YQ0ZoQk9zZyIsImdubyI6MCwiZXhwIjoxNzAyMzA2ODA3LCJ0eXBlIjozLCJpYXQiOjE3MDIzMDMyMDcsImFpZCI6IlNQc3FveHdqVHBxTy1TTGh0bDMwcncifQ.Ve49nYm4VnyhhYXMkgIE1AfeKCshY_8hdjVQgEXCnUJDL8q3hDT2cqapFkQhqFJ2z0zeyiVd8P2JTgIZd8Wv8w

Thanks for your help

Hi,

Are the subsequent requests failing even after generating a new access token?

There is no call after a Token error.
I rerun the generation of a new Token and repeat the operation that failed.

@EVant

  • can you confirm that the app is still active (not deactivated or deleted) ?
  • can you confirm that the user is still part of the same account?

If yes, can you paste the complete error that you receive from Zoom in curl format?

I confirm a positive answer to both questions.
The error doesn’t occur consistently and hasn’t reappeared since the post.

[quote=“Eric, post:1, topic:99931, full:true, username:EVant”]
Hello

I’ve been having problems lately with the automatic closure of a session.
The script runs smoothly, but there are a few calls that generate errors with the API: https://api.zoom.us/v2/meetings/meeting_id/status
The log below shows the generation of a token and its use a few milliseconds later.

2023-12-11 15:00:07,391 INFO:HTTP Request: POST https://zoom.us/oauth/token?grant_type=account_credentials&account_id=SPsqoxwjTpqO-SLhtl30rw "HTTP/1.1 200 OK"
2023-12-11 15:00:07,392 INFO:New Token: Bearer eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6ImQyOWViYjc4LTdmNGMtNDIzNC04NGI0LTI5MmViYTBlZjRiZSJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFYWpTZGdPcVJVT0RzN1JHUVFZVTN3IiwidmVyIjo5LCJhdWlkIjoiY2M3Y2JhZTQ1MzY4MGYzYTdiZmUyNjAyZDU2NGQ0MzUiLCJuYmYiOjE3MDIzMDMyMDcsImNvZGUiOiJiMUN3NXdWSVFGaXVfdWR3YjRtZ2tnRUNyMmJhSTZLU1EiLCJpc3MiOiJ6bTpjaWQ6Y2duNUN0aHZTX2FXdW5YQ0ZoQk9zZyIsImdubyI6MCwiZXhwIjoxNzAyMzA2ODA3LCJ0eXBlIjozLCJpYXQiOjE3MDIzMDMyMDcsImFpZCI6IlNQc3FveHdqVHBxTy1TTGh0bDMwcncifQ.Ve49nYm4VnyhhYXMkgIE1AfeKCshY_8hdjVQgEXCnUJDL8q3hDT2cqapFkQhqFJ2z0zeyiVd8P2JTgIZd8Wv8w
2023-12-11 15:00:07,392 INFO:ClientId : cgn5CthvS_aWunXCFhBOsg
2023-12-11 15:00:07,397 INFO:PUT:https://api.zoom.us/v2/meetings/82322546443/status
2023-12-11 15:00:12,420 ERROR:Error : 
2023-12-11 15:00:12,420 ERROR:Headers Error : https://api.zoom.us/v2/meetings/82322546443/status
2023-12-11 15:00:12,421 ERROR:Client Header : Headers({'accept': '*/*', 'accept-encoding': 'gzip, deflate', 'connection': 'keep-alive', 'user-agent': 'python-httpx/0.24.0', 'authorization': '[secure]', 'content-type': 'application/json'})
2023-12-11 15:00:12,421 ERROR:authorization : Bearer eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6ImQyOWViYjc4LTdmNGMtNDIzNC04NGI0LTI5MmViYTBlZjRiZSJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFYWpTZGdPcVJVT0RzN1JHUVFZVTN3IiwidmVyIjo5LCJhdWlkIjoiY2M3Y2JhZTQ1MzY4MGYzYTdiZmUyNjAyZDU2NGQ0MzUiLCJuYmYiOjE3MDIzMDMyMDcsImNvZGUiOiJiMUN3NXdWSVFGaXVfdWR3YjRtZ2tnRUNyMmJhSTZLU1EiLCJpc3MiOiJ6bTpjaWQ6Y2duNUN0aHZTX2FXdW5YQ0ZoQk9zZyIsImdubyI6MCwiZXhwIjoxNzAyMzA2ODA3LCJ0eXBlIjozLCJpYXQiOjE3MDIzMDMyMDcsImFpZCI6IlNQc3FveHdqVHBxTy1TTGh0bDMwcncifQ.Ve49nYm4VnyhhYXMkgIE1AfeKCshY_8hdjVQgEXCnUJDL8q3hDT2cqapFkQhqFJ2z0zeyiVd8P2JTgIZd8Wv8w

Thanks for your help
[/quote]

It seems there might be an issue with the API call to retrieve the status of a Zoom meeting. The script successfully generates a token, but when attempting to use it for the API call, an error occurs. The error suggests a problem with the headers during the HTTP request.
To address this, you may want to check the authorization header, which includes the generated token. Ensure that the token is being properly formatted and included in the request. Additionally, verify that the meeting ID used in the API call is correct.
If the issue persists, you may need to review the Zoom API documentation for any specific requirements or changes in the API endpoint for meeting status.

Thank you for your answer.
I’ve put in the log all the informations Header, Bearer and call sequence.

This script is so rudimental that I have no margin for errors.

Since my post (1 month) and without any change, it hasn’t occured again. I assume it’s a zoom servers issue