500 error when updating exhibitors

API and Webhooks
1

API Endpoint(s) and/or Zoom API Event(s)

patch /zoom_events/events/{eventId}/exhibitors/{exhibitorId}

Description
I am trying to update an exhibitor using the PATCH method. I get an HTTP 500 error An error was encountered when processing your request.

I have been able to update sessions and speakers with no issues, I’ve only seen this problem with exhibitors.

I have the following scopes enabled.

['zoom_events:read:event:admin',
 'zoom_events:read:exhibitor:admin',
 'zoom_events:read:list_events:admin',
 'zoom_events:read:list_exhibitors:admin',
 'zoom_events:read:list_sessions:admin',
 'zoom_events:read:list_speakers:admin',
 'zoom_events:read:list_sponsor_tiers:admin',
 'zoom_events:read:session:admin',
 'zoom_events:read:speaker:admin',
 'zoom_events:update:exhibitor:admin',
 'zoom_events:update:session:admin',
 'zoom_events:update:speaker:admin',
 'zoom_events:write:exhibitor:admin',
 'zoom_events:write:session:admin',
 'zoom_events:write:speaker:admin']

Error?

<Response [500]>
b'{"code":500, "message":"An error was encountered when processing your request"}'

How To Reproduce
Running from a python script. I can create an exhibitor, and get the information:

    r = requests.get(ZOOM_API_URL + f"/zoom_events/events/{event_id}/exhibitors/{item_id}",
                     headers={"Authorization": f"Bearer {zoom_token}"})

but if I try to update it with

    r = requests.patch(ZOOM_API_URL + f"/zoom_events/events/{event_id}/exhibitors/{item_id}",
                     headers={"Authorization": f"Bearer {zoom_token}", "Content-Type": "application/json"},
                     json={"name": "new name"})

i get the HTTP 500 error.

2

Hi @SocRSE
Thanks for reaching out to us!
Could you please share with me the tracking ID of this request so I can escalate this?

3

Hi,
I am not completely sure what you mean by tracking ID.
The event ID is WhLtcgeyQ9W1ihzxcOvoyQ
And I get the same with any exhibitor id, e.g. 1F7wd9PkSKOAVf-d1yakeA or Kdyu70bfS1udoF_oP9I60Q

4

The tracking ID is included in the response headers of your request (x-zm-trackingid) @SocRSE

5

For the successful GET, WEB_0c79ae8909717c8a56bc193ca17de533

For the failing PATCH, WEB_7239e0df84b14e7ceccbaee049e65097

Thanks

1 Like
6

Thanks @SocRSE
I created an internal ticket for our Engineering team to look furhter into this
( ZSEE-178296 internal ticket number for reference)
I will keep you updated

1 Like