# GET /users/{userId}/meetings not returning future meetings

**URL:** <https://devforum.zoom.us/t/get-users-userid-meetings-not-returning-future-meetings/89775>\
**Category:** Meetings\
**Created:** [June 7, 2023, 2:45pm UTC](https://devforum.zoom.us/t/get-users-userid-meetings-not-returning-future-meetings/89775 "2023-06-07T14:45:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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 7, 2023, 4:57pm UTC](https://devforum.zoom.us/t/get-users-userid-meetings-not-returning-future-meetings/89775/2 "2023-06-07T16:57:40Z")

</div>

Hi @mdickens ,

> [@mdickens](#):
>
> No matter what date I put as the “to” date with the type set to “scheduled” or “upcoming”, it always returns a “to” date of tomorrow.

Could you please check if somehow a space is present before “to” and “from” in the URL as a similar behavior occurred with a previous developer:

> [@How to pass parameters into the recordings api](https://devforum.zoom.us/t/how-to-pass-parameters-into-the-recordings-api/82335/9):
>
> Somehow spaces end up before “to” and “from” and that appears to be causing the issue. I have now resolved it. The original problem appears to be that you can’t specify a from without a to date. These are provided as query parameters, so the JSON reference in the documentation is wrong.

---

_[View the full topic](https://devforum.zoom.us/t/get-users-userid-meetings-not-returning-future-meetings/89775)._
