Error response for Zoom Rest API

Error response {

"code": -1,

"message": "Unable to execute HTTP request: dynamodb.us-east-1.amazonaws.com"

}

{

"code": -1,

"message": "execute SQL error,  method: PRIMARY.MeetingOccurrenceInfoMapper.getItems, rawSQL: SELECT\\n            meeting_number,\\n            occurrence,\\n            account_id,\\n            meeting_id,\\n            create_time,\\n            modify_time\\n        FROM ZMWEB_MEETING_OCCURRENCE_INFO\\n        WHERE meeting_number = #{meetingNumber}"

}

when call https://api.zoom.us/v2/meetings/{meetingID}

Hi @Eve1,

I’m experiencing the exact same issue right now!

Same error when creating meetings:

{
  "code": -1,
  "message": "execute SQL error, method: PRIMARY.MeetingOccurrenceInfoMapper.getItems, rawSQL: SELECT\n            meeting_number,\n            occurrence,\n            account_id,\n            meeting_id,\n            create_time,\n            modify_time\n        FROM ZMWEB_MEETING_OCCURRENCE_INFO\n        WHERE meeting_number = #{meetingNumber}"
}

My case:

  • Endpoint: POST /v2/users/{userId}/meetings (creating scheduled meeting)
  • Started happening: Today, October 20, 2025 around 9:54 AM GMT+2
  • Request format: Verified against API documentation - everything is correct
  • Authentication: Token is valid

This appears to be an internal database issue on Zoom’s side. The error message clearly indicates a SQL query failure in MeetingOccurrenceInfoMapper.

Impact:
Our Learning Management System cannot create scheduled meetings for students. Multiple users are affected.

Attempted to reach support:

  • Unable to submit a support ticket (technical issues on support portal)
  • Tried calling support: was #200 in queue with 80+ minutes wait time
  • This seems to indicate a widespread issue affecting many customers simultaneously

Has anyone from Zoom team acknowledged this issue? It seems to be affecting multiple developers at the same time.

@zoom-support-team - Could you please investigate this urgent issue? The support channels appear to be overwhelmed, which suggests this is a major incident.

Thanks!

Hi @Andre @Eve1
Thanks for reaching out to us.
We are currently looking into this and will get back to you with an update soon