# Participant email casing changes based on next\_page\_token presence in response

**URL:** <https://devforum.zoom.us/t/participant-email-casing-changes-based-on-next-page-token-presence-in-response/52274>\
**Category:** API and Webhooks\
**Created:** [June 11, 2021, 3:33pm UTC](https://devforum.zoom.us/t/participant-email-casing-changes-based-on-next-page-token-presence-in-response/52274 "2021-06-11T15:33:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dzuczek](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dzuczek/32/25035_2.png) [@dzuczek](https://devforum.zoom.us/u/dzuczek)\
**Post date:** [June 11, 2021, 3:33pm UTC](https://devforum.zoom.us/t/participant-email-casing-changes-based-on-next-page-token-presence-in-response/52274/1 "2021-06-11T15:33:57Z")

</div>

When retrieving a paginated list of meeting attendees, calling /report/meeting/123456789/participants the following payload is returned:

```auto
{
            "id": "0WS_GCm0Rj2tysg7jZOtiQ",
            "user_id": "16783360",
            "name": "John Smith",
            "user_email": "jsmith@domain.com",
            "join_time": "2021-06-03T17:25:49Z",
            "leave_time": "2021-06-03T17:30:33Z",
            "duration": 284,
            "attentiveness_score": "",
            "failover": false,
            "customer_key": ""
        },
[...]
"next_page_token": "abcdefhijkl"

```

But then calling this same call with page\_size=300 (which means for this meeting, no pagination necessary) the payload looks like this:

```auto
{
            "id": "0WS_GCm0Rj2tysg7jZOtiQ",
            "user_id": "16783360",
            "name": "John Smith",
            "user_email": "JSMITH@DOMAIN.COM",
            "join_time": "2021-06-03T17:25:49Z",
            "leave_time": "2021-06-03T17:30:33Z",
            "duration": 284,
            "attentiveness_score": "",
            "failover": false,
            "customer_key": ""
        },

(next_page_token not present)

```

It seems the email is being lowercased() when using pagination. This affects some aggregation routines on our end as user\_email is used as a key to sum up the duration.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [June 14, 2021, 7:41pm UTC](https://devforum.zoom.us/t/participant-email-casing-changes-based-on-next-page-token-presence-in-response/52274/2 "2021-06-14T19:41:10Z")

</div>

Hi @dzuczek thank you for inquiring about this. I have a few questions to better support you with this:

- How are you sending this request? Are you using any API testing tools? (i.e. Postman, curl, etc. or your own environment?)

If you’re seeing this consistently across different environments, I definitely want to take a closer look. Could you please submit the exact raw request, the email in the request body, and timestamp of the request to [developersupport@zoom.us](mailto:developersupport@zoom.us). This will help us to check our logs and inquire on our end. Please also reference this thread in the email.

Thank you

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 15, 2021, 5:41am UTC](https://devforum.zoom.us/t/participant-email-casing-changes-based-on-next-page-token-presence-in-response/52274/3 "2021-07-15T05:41:37Z")

</div>

Closed on July 15, 2021, 5:41am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
