Hello Bubble Community,
I have a following use case:
I can expose a public Workflow API called “get-availabilities” that has an action “Return data from API” it is a JSON response that in bubble root URL format is accessed on the following Workflow API root URL + workflow api name
https://mybackendapp.io/version-test/api/1.1/wf/get-availabilities
but I have to add a path segment /1/ like following:
https://mybackendapp.io/version-test/api/1.1/wf/1/get-availabilities
renaming the api workflow to “1/get-availabilities” is not possible since "/"is not allowed
Anyone has any idea how to do insert or redirect to that specific target URL where the Workflow API response action is initiated?
This is the API System’s requirement on how it want to send and receive requests on URLs:
https://integrator.getyourguide.com/documentation/supplier_endpoints
So that /1/ added to Workflow API root URL makes the public GET API endpoint name “lost”:
{“statusCode”:404,“body”:{“status”:“NOT_FOUND”,“message”:“Workflow not found 1”}}
Hi @kalinovic.nebojsa , were you able to find a solution?
For custom root directories when custom URL specifications are required by API providers I added and used XANO no code in my stack where you can set any preferred logic for including custom URL endpoints.
Interesting problem that they don’t let you set your own webhook URL..
Best approach is to spin up a little Cloudflare worker that receives the request on a URL in that form and forwards it to Bubble
