Dear Louie,
Usually you can do it like this,
1. you publish the gateway service with resolution path similar like this,
/customer*
it allows you to call the gateway with different uri, for example,
http(s)://<gateway>:<port>/customer
http(s)://<gateway>:<port>/customer/2
2. you parse the uri in your policy
use split variable assertion or regex assertion to pick up the customer id from ${request.http.uri}, and set the value to a context variable, for example ${customerid}
3. then in the route assertion, you can set the url as,
http://machine:8081/api/customer/${customerid}Regards,
Mark
Original Message:
Sent: 11-12-2019 01:28 PM
From: Louie Kwan
Subject: Overloading API URL
------------------------------
Louie
------------------------------