Backend Workflow API doesn’t accept segmented path parameters

Need help
1

Hi everyone,

I’m currently building an API integration with GetYourGuide to replace a third-party booking system and migrate everything to my Bubble website.

Their API uses some routes structured like this:
GET …/products/:productId/pricing-categories

Issue

Bubble’s Backend Workflow API does not seem to support endpoint names that include path segments with path parameters inside them (e.g. :productId), not even if the parameter is at the end of the path, and can only read values passed through query parameters or JSON body..

When GetYourGuide triggers the request in the exact format above, Bubble receives:

  • Empty request body
  • No captured parameters
  • 401 Unauthorized response (even when the workflow is publicly exposed and set to no auth required)

(Instead of being triggered directly by GetYourGuide, this request is currently being sent from Postman using an exported collection from the GetYourGuide API documentation. This collection contains all the required request structures and expected response formats defined by GetYourGuide. In practice, this simulates the exact same request format that GetYourGuide would send)

I’ve already tested:

:white_check_mark: Endpoint exposed as public workflow
:white_check_mark: Allow run without authentication
:white_check_mark: Other inbound workflows work fine (with query params or body JSON)

image
image1086×581 55.2 KB

*Postman screenshot

image
image824×711 25.3 KB

Bubble.io screenshot (Backend Workflow API)

My question

  • Is this a known limitation of Backend API Workflows, or could this be a bug/feature gap?
  • Has anyone successfully handled inbound URLs with an internal path parameter like /products/:productId/pricing-categories in Bubble?

I think I can solve this via a rewrite/proxy, but I’d like to avoid that if this is simply an overlooked feature or there’s a Bubble-native solution I missed.

Any clarification or guidance would be greatly appreciated!

Thanks!

2

Yes, this is a limitation of Backend API Workflows, unfortunately, it’s not possible to use paths in endpoint names.

If you really need (or want) to create endpoints with paths, you’ll have to do it through a proxy to get the desired URL structure and then rewrite them to point to Bubble.

2 Likes