Support for URL path parameters

With the addition of custom URLs for apps, I'd love the ability to use URL path parameters instead of query parameters, especially for things like ID's.

For example, currently I have to do:

https://my.retool.domain/app/events?event_id=12345

I'd love to do:

https://my.retool.domain/app/events/12345

This would create a cleaner path that's easier to share with users. Would Retool possibly support this in a future release? As a starting point implementation, perhaps Retool could just make any part of the path (between the / and any ? that may be set) accessible in app via something like urlparams.pathParam or similar.

1 Like

Hey Matt! That is an excellent suggestion and I totally agree that we should support dynamic url paths. We’re in the middle of developing support for multipage and are thinking about this on the roadmap. No concrete timelines yet, but this is helpful to know you’re looking for this. Thanks!

1 Like

For folks following along, multipage apps (the default app experience) support custom page urls, but at this time, we don't support dynamic page urls. Only the search and hash params can be dynamic (i.e. ?event_id=12345).

If your page will always display event 12345, you can make the url look like this: https://my.retool.domain/app/app-id/events/12345

If you have an events page that will dynamically show different events (12345, 67890, etc), you can follow this topic for updates on the feature request. It isn't on the near term roadmap, but when that changes, we'll follow up here!