Hi,

Need guidance for my below use case.

currently we have existing catalog DEV and there are existing consumer who are using this dev endpoint from their application.

Now we are trying to create another Catalog parallel to DEV. E.g. Dev-Internal and Dev-External using same Datapower Gateway.

Now My understanding is that even developer portal URL is different but the API endpoint would be same so that we don't impact in terms of endpoint.

And correct me if we can keep the existing endpoint to the new catalog by using by setting the Vanity API endpoint.

And gradually plan is to retire the old catalog once everyone moves to new Catalog.

Any suggestions/feedback.

No you do not want to attempt to have the same api endpoint on the same gateway in two catalogs.

that is not going to go well.

Thank you Chris for providing me all the guidance. We are currently planning to expose our developer to different types of consumers to I am trying to do all kind of research and POC.

So in regards to the above question:, do we have any guideline or best practice that we can follow.

So is there any restriction on the API endpoint. e.g. below

Lets say Catalog name : External-Dev

Portal URL:  https://host/external/dev  -- I followed https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=catalogs-configuring-sub-paths-developer-portal-sites

api endpoint : https://api,xx./external/dev  --is there any restrictions on the api endpoint that it should end with catalog name like https://api,xx./external-dev