This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 22%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGV%3C/text%3E%3C/svg%3E)
HI,
I have an existing REST API, which consumers access from APIM. I have to add some new logic (no API contract change), which i don't want to add in existing API implementation. Can I create a new API endpoint, which will call the existing API and then do new logic and return response to clients, without client's being aware that response is from new API endpoint?
@Guru V You can refer to APIM revisions if there are minor and non-breaking changes to an API. When you want to make changes, create a new revision. You can then edit and test API without disturbing your API consumers. When you're ready, you then make your revision current.
@MayankBargali-MSFT , thanks for your reply.
I am looking for an option to redirect clients to a different endpoint. it is not for testing purpose like revision. Presently my API is giving json response which is big in size, so I am looking for an option of using Azure CDN to give the same json to clients (to take benefit of CDN for faster speed of transfer to clients.)
When my clients call my current API (behind APIM), the existing API should redirect client to CDN location to get JSON. this being totally transparent to client.
Is this scenario possible. if not any other option to deliver big size response to clients (client code is external and can be in any technology)
@Guru V I believe your workflow is Client --> APIM --> backend service. As you don't want any changing at the client and want to use cache so your backend service is not called every time rather than cache the content then you can leverage the internal/external cache in the APIM as documented here. Now you need to write the policy to verify if the data is already present in the cache or not.
In case if you still want to leverage the CDN then your workflow will be Client --> APIM --> CDN --> backend service and your APIM backend service will now be CDN endpoint rather than backend service.