Why does the "list_webinar_registrants" step return a 404 error for older webinars in Pipedream?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

So I’ve got 2 steps retrieving Zoom webinar data - “list_webinar_registrants” and “list_webinar_participants”. In pipedream I there is a “webinar” field that presents a lookup of recent webinars. If I enter the ID of a webinar that is older than “recent” it will retrieve the data in the “list_webinar_participants” step. However in the “list_webinar_registrants” step it returns:
Note: this is the same account, same webinar ID and tested on the same AND different workflows.
Error - Request failed with status code 404
{“code”:3001,“message”:“Meeting does not exist: 86318950792.”}
DETAILS

    at null.createError (/tmp/__pdg__/dist/code/35288b562210262f76682830b4f1709e1c9947e2cfc2a53a9050e130418e3951/node_modules/.pnpm/axios@0.21.4/node_modules/axios/lib/core/createError.js:16:15)
    at null.settle (/tmp/__pdg__/dist/code/35288b562210262f76682830b4f1709e1c9947e2cfc2a53a9050e130418e3951/node_modules/.pnpm/axios@0.21.4/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/tmp/__pdg__/dist/code/35288b562210262f76682830b4f1709e1c9947e2cfc2a53a9050e130418e3951/node_modules/.pnpm/axios@0.21.4/node_modules/axios/lib/adapters/http.js:269:11)
    at IncomingMessage.emit (node:events:525:35)
    at null.endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2

: This seems related:

It looks like the List Past Webinar Registrants API will only return data for webinars that haven’t expired.

You’ll want to use our Reports APIs for older/expired meetings.

3

Does Pipedream have the reports api as steps?

4

Actually, if we read further… :confounded:

It doesn’t look like there is a way to get a report of the registrants via the API. If you would like this feature to be considered for a future release, I recommend posting in the #feature-requests category.
In the meantime, you can use the Let Meeting Registrants API for recent meetings and then retain that data for the future. It doesn’t seem there is a way to obtain historical data via the API though.

5

ahhh okay - it would be a fringe case for me but its good to know