Hey @ksmithmim - great question! While you can pass some event information in the redirect URL, the location is not a piece of data that is accessible in the URL. 

As an alternative, our API supports creating a webhook subscription. We will send POST requests to the URL you provided for newly scheduled or canceled events. You can get this data from the webhook and display it on your redirect page. The webhook payload contains the scheduled_event object which has location inside it, so you can absolutely create a new subscription to start receiving those payloads and then do what you need with them! Here is some more helpful information: 

Here is the data object of the v2 API webhook. The webhook subscription only allows for a uni-directional push of information. If you are making this webhook for internal, private use only, you can create a personal access token to use as the token value. If you are making this webhook for an external application, please note that our API uses the OAuth 2.0 Authorization Framework. You will need to follow the Getting Started guide to receive OAuth credentials to create access tokens for this call.

You can choose to either create a webhook with an individual user scope, or, if you are using an access token associated with an Owner or Admin, you can create a webhook subscription with an organization scope to receive the data for all users within your organization. More details about the scope can be seen in the webhook documentation.

Here is our developer portal/API reference - you can use this when working with your web developer to look into a work around!