Hi Farhan,
You can use “Contains” instead of “Equals”. If your use case is to route the incoming request to backend as is then you can use ${sys:resource_path} in the routing rule. This will help in one to one mapping of incoming request and native API.
You can also check the attached link for more details on variables supported. Reverb
@Prabaa For the resource defined by GET /booking/{bookingId}, how can i get the PATH parameter(bookingId) value in a webMethods flow service which is invoked in the request processing phase? Any suggestions.
I see that the RequestSpec doesnt have any variables for this as part of the request cycle.