Recording.Completed event schema has id field with data type as Integer but Zoom sends value exceeding the range for id


Recording.Completed event schema has id (unique identifier of the meeting /webinar that was recorded) field with data type as Integer (format :int64) but Zoom sends value (as part of webhook notification) exceeding the range .

JSON schema (as part of documentation) : id field

“object”: {
“type”: “object”,
“properties”: {
“id”: {
“type”: “integer”,
“description”: “Unique Identifier of the Meeting/ Webinar that was being recorded.”,
“format”: “int64”

Payload data :

“payload”: {
“account_id”: “fSi7l9GxSZmk3YgfTbXPnQ”,
“object”: {
“uuid”: “EvU6SpWRQXOhocWctE4dbA==”,
"id": 89184074030,
“account_id”: “fSi7l9GxSZmk3YgfTbXPnQ”,

Please share the correct/updated JSON schema for Recording.Completed event.

The full error message or issue you are running into.

Exception occured while parsing the notification event {}
com.fasterxml.jackson.databind.JsonMappingException: Numeric value (89184074030) out of range of int (-2147483648 - 2147483647)

Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT App .

Which Endpoint/s?
Knowing the API endpoint/s can help us to identify your issue faster. Please link the ones you need help/have a question with.

Endpoint: App Marketplace

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Record a meeting using account
  2. Stop the recording and end the meeting for the recording to get uploaded to Zoom
  3. The Request Body of the Recording.Completed event has id (unique identifier of the meeting /webinar that was recorded) has data exceeding the range of Integer data type.

Screenshots (If applicable)
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Please share an Open API compliant JSON schema for Recording.Completed event so that using Open API code generator we could generate the classes required. Currently the schema provided in docs fails Open API validation

Hey @hylandmediakolkata,

Thank you for reaching out about this! Our engineering team is working to provide a refactored Open API specification. I don’t have a timeline on it just yet but our team is aware of this issue and working towards a fix.


1 Like