This is a FYI to other developers who are attempting to create ticket types for their events. I was getting the dreaded Open API Gateway Rewrite Error, Please Config Field Mapping
when sending the following request:
POST https://api.zoom.us/v2/zoom_events/events/GIV8lK93R2ylkDYWFVQRSA/ticket_types
{
"name": "VIP backstage pass",
"currency": "CAD",
"start_time": "2025-07-04T13:17:02Z",
"end_time": "2025-07-11T13:16:57Z"
}
After a lot of trial and errors I discovered that attendance_type
is required despite the fact that documentation does not indicate it is required. Furthermore, the documentation says that there are three possible values for this attendance type field: virtual, in-person and hybrid. Turns out, the API returns {"code":400, "message":"Only in person ticket is allowed"}
if you specify virtual or hybrid. Only in-person
is acceptable.
@elisa.zoom Please pass along this feedback to the docs team to improve Create an event ticket type. Thanks.
2 Likes
Thanks @desautelsj
Happy to report this too
Would you be able to share the entire request URL and the tracking id for this error you are reporting please?
1 Like
The entire request is in my original comment, including the URL and the JSON payload. Give me a few minutes I’ll run my tests again to get you a tracking id.
1 Like
Ok, now I’m confused: I am no longer able to reproduce this problem. I was able to reproduce it consistently last week but today it’s working just fine when I omit the attendance_type
from my request.
Here’s what my latest test looks like:
REQUEST:
POST https://api.zoom.us/v2/zoom_events/events/QSXcOGRnRbWGwcxc5k08yg/ticket_types
{"name":"Backstage pass","start_time":"2025-07-09T18:42:18Z","end_time":"2025-07-16T18:42:13Z","currency":"CAD"}
RESPONSE:
HTTP/1.1 201 Created
Date: Wed, 09 Jul 2025 18:42:23 GMT
x-zm-trackingid: WEB_f563e7802ae5997f15f89146f1b55747
{"ticket_type_id":"IMfO5eyZQG-Vd_Vp0dfsag"}
Is it possible something changed in the intervening several days? Is it possible the Open API Gateway Rewrite Error
message could be the indication of some other intermittent issue? Is it possible this error has nothing to do with the presence/absence of the attendance type property?
1 Like
Hi @desautelsj
I believe our engineering team might have addressed the issue with attendance_type already.
Although I see the open ticket still. Let me ask when this will be fixed