Version identifier not working

Christian Haugseng Smebye 0

Hi,

I have attempted to create a new version of an API via the context menu (...) and "Add version". I set the "Version identifier" to 3.1 and changed, among other things, the Web service URL.

When I try to access the new version of the API, I get "Unsupported API version". https://video2.skills-academy.com/en-us/azure/azure-app-configuration/rest-api-versioning#unsupported-api-version

When I try with the original version (3), it works fine.

If I try with a version I know doesn't exist, I get a 404 "Resource not found," as expected.

What have I set up incorrectly?

(I am running on the Pricing tier Basic and platform version stv2 and the subscription key is valid.) User's image

User's image

LeelaRajeshSayana-MSFT 14,831 Reputation points Microsoft Employee

2024-09-04T16:57:37.1766667+00:00

Hi @Christian Haugseng Smebye Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

Apologies for the delay in handling this issue. The settings you have shared from the above image seem accurate and it looks like the API version is assigned to a product.

I have tested creating different versions of API following the documentation Publish multiple versions of your API and I could not encounter the error response you face.

Although, I did not try changing the backend service URL for the created version. When you change the backend service URL, the APIM forwards the requests from the clients to this end point and shares the response back to the client. Does your modified service URL end point and the initial version of the API support the same specification API's?

I appreciate it if you can add a new API end point and point it to the changed back-end URL and see if it returns the expected result. If it succeeds, please try to create a version from this and test the created version.

Please keep us posted on your findings. Kindly share all the modifications you have made while creating a version.

1 answer

Christian Haugseng Smebye 0 Reputation points

2024-09-04T18:15:03.1733333+00:00

Hi and thanks for reply @LeelaRajeshSayana-MSFT !

I have tried using the same backend service, but I’m still getting the same result.

In the API where I changed the backend service, it supports the same specifications, and my request is configured correctly. The request reaches the API since I receive the "Unsupported API version" response, but it doesn’t seem to pass through the APIM.

The version identifier is in the header.

Any clues?
Please sign in to rate this answer.
LeelaRajeshSayana-MSFT 14,831 Reputation points Microsoft Employee

2024-09-06T14:26:40.01+00:00

Hi @Christian Haugseng Smebye I have reached out to you via offline message and shared next steps on this issue. Please follow the steps suggested on the message. Let us know if you have any issues accessing the message.

Christian Haugseng Smebye 0 Reputation points

2024-09-09T07:57:25.4133333+00:00

Thanks!
I will follow up.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Version identifier not working

1 answer

Your answer