For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create Event Deep Links

Overview

PodPlay supports deep linking to both the Events tab and the Book tab of your Club's App. A deep link is a URL that takes a Customer directly to a pre-filtered view, whether that's a filtered Event list or a specific booking experience (with an optional date already selected). This is useful for marketing campaigns, social media posts, QR codes, email newsletters, or any situation where you want Customers to land on exactly the right part of the App without having to navigate or filter.

Deep links are built using your Club's unique subdomain and a set of optional query parameters and path segments appended to the base URL.

Deep Linking to Events

URL Structure

Every deep link starts with your club's base Events URL:

https://[clubname].podplay.app/community/events

To filter the results, you append one or more query parameters to the end of the URL. Query parameters follow this pattern:

  • The first parameter is preceded by a ? (question mark)

  • Each additional parameter is separated by a & (ampersand)

  • Parameter values with spaces use a + in place of each space

The general structure is:

https://[clubname].podplay.app/community/events?[parameter1]=[value1]&[parameter2]=[value2]

Parameters

There are four parameters you can use, in any combination:

Parameter
What it filters
Format
Example value

level

Skill levels

Text

Beginner, Intermediate, Advanced

type

Event types

Text (spaces as +)

Open+Play, Clinic, League, Social+Play

tag

Custom tags

Text (spaces as +)

Members+Only, Drill+and+Play

date

Calendar dates

YYYY-MM-DD

2026-04-22

You only need to include the parameters relevant to your use case. Any parameter you leave out will not be applied as a filter.

Parameter values are case-sensitive and must exactly match the level names, Event types, and tags configured in your Dashboard for your environment. If no events match the combination of filters in the URL, the page will display empty; this is expected behavior.

Examples

Filter by a single tag:

Displays all events tagged "Members Only" (this is only an example; if you do not have this tag in your environment, it will not work).


Filter by level and event type:

Displays Advanced-level Open Play events. The level parameter comes first, followed by &, then the type parameter.


Filter by event type and tag:

Displays Open Play events tagged "women." The type parameter comes first, followed by &, then the tag parameter.


Filter by all three parameters:

Displays Intermediate Open Play events tagged "women." Each additional parameter is appended with &. If no event matches all three filters simultaneously, the page will show no results — this is not an error; it simply means no events currently have that exact combination.


Filter by date:

Opens the event calendar to a specific date. The date is added as a date query parameter in YYYY-MM-DD format.


Filter by date combined with other parameters:

Opens the calendar to April 22, 2026, filtered to Open Play events tagged "women." The date parameter works alongside any combination of level, type, and tag.


  1. Start with your base URL: https://[clubname].podplay.app/community/events

  2. Add a ? immediately after events (no space)

  3. Add your first parameter in the format key=value (e.g., type=Open+Play)

  4. If you need a second parameter, add & immediately after the first value, then add the next key=value pair

  5. Repeat step 4 for any additional parameters

  6. Replace any spaces in parameter values with +

Example build:

Step
URL

Base URL

https://[clubname].podplay.app/community/events

Add event type

https://[clubname].podplay.app/community/events?type=Open+Play

Add level

https://[clubname].podplay.app/community/events?type=Open+Play&level=Intermediate

Add tag

https://[clubname].podplay.app/community/events?type=Open+Play&level=Intermediate&tag=women

Add date

https://[clubname].podplay.app/community/events?type=Open+Play&level=Intermediate&tag=women&date=2026-04-22

Does the order of parameters in the URL matter?

No. The parameters can be added in any order and will produce the same filtered result.

What if I use a level, type, or tag that doesn't exist in my Dashboard?

The page will load but display no events. Double-check that the value in your URL exactly matches what is configured in your environment, including capitalization and spacing.


Deep Linking to Reservations

Overview

If your Club offers multiple booking experiences, for example, separate court types such as pickleball, padel, or table tennis, you can deep link Customers directly to a specific booking experience on the Book tab of your App. You can also include a specific date in the link so the App opens directly to that day.

The easiest way to discover your Reservation deep links is to open the front-end of your web app in a browser, navigate to the Book tab, and click the quick filters at the top of the page. The URL in your browser will update as you apply filters and select dates; that URL is your deep link.

URL Structure

Every Reservation deep link starts with your Club's base Book URL:

Where [location] is the URL slug for your specific location (visible in your browser when you navigate to the Book tab).

To filter by booking experience, append a pod query parameter:

To also open the calendar to a specific date, insert the date in YYYY-MM-DD format into the URL path, between the location and the query parameter:

Parameters

Element
Where it appears
Format
Example

Location

In the URL path, after /book/

Kebab-case slug

st-pete

Date (optional)

In the URL path, after the location

YYYY-MM-DD

2026-04-21

pod

Query parameter after ?

Kebab-case slug

pickleball-courts

The pod value must match the slug for that booking experience as configured in your environment. Use the front-end quick filters to confirm the exact slugs for your Club.

Examples

Link to a specific booking experience (no date):

Each link opens the Book tab filtered to that court type, with the calendar defaulting to today's date.

Link to a specific booking experience on a specific date:

The date is inserted into the path (after the location slug and before the ?), and the calendar opens directly to that day filtered to the specified court type.

Rather than building Reservation deep links manually, the simplest approach is to let the app generate them for you:

  1. Open your Club's web app in a browser and navigate to the Book tab.

  2. Use the quick filters at the top of the page to select the booking experience you want to link to (these are only available if you have different booking experiences).

  3. Optionally, select a date on the calendar carosel.

  4. Copy the URL from your browser's address bar; this is your deep link.

What if my Club only has one booking experience?

The pod parameter is only needed when your Club has multiple booking experiences. If you have a single experience, the base Book tab URL (https://[clubname].podplay.app/book/[location]) will take Customers directly to it.

How is date filtering different between Events and Reservations?

The two use different URL structures. For Events, the date is a query parameter (?date=YYYY-MM-DD) appended after the ? alongside other filters. For Reservations, the date is inserted directly into the URL path (/book/[location]/YYYY-MM-DD) before the ?.

Last updated

Was this helpful?