Malformed api.id value error when using apim workflow in Logic App

Anthony Bateman 26 Reputation points
2020-07-16T12:16:28.44+00:00

I'm trying to call an API operation that I have built myself from a Logic App. When I save the solution, I get the following error:

Failed to save logic app logic-batch-not-in-loading-order- v1. The workflow operation 'test-call' of type 'ApiManagement' has a malformed value '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx- xxxxxxxxxxxx/resourceGroups/xxxx%xx%A4_automati... workflow/apis/xxxxxx' for property 'api.id'. The expected format is
'/subscriptions/{subscriptionld}/resourceGroups/{resourc...

I do not know where the property api.id is defined; I have not set it and I don't know why it is malformed.

Advice?

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
1,908 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,965 questions
{count} votes

Accepted answer
  1. svijay-MSFT 5,226 Reputation points Microsoft Employee
    2020-07-17T14:19:29.283+00:00

    Hello @AnthonyBateman-3017,

    On looking closing on the error message, I see the below url

    ......./resourceGroups/xxxx%xx%A4_automati.........

    There is a %xx% , I am assuming there is a special character in the resource group name. Usually the special characters are encoded in this format.

    As per the document here, the resource group should match the Regex pattern: ^[-\w._()]+$ and not a lot special characters is allowed in the name.
    I believe it is because of the presence of a non allowed special character in the resource group name - you are encountering this issue. Recommend you to check your resource group name in any regex testing platform. using the above pattern.

    Upon researching further, I came across a know issue that is documented here - https://github.com/microsoft/vscode-azureappservice/issues/686 - Azure allows resource groups being created with the name containing a special character ä though it is not supposed to. This is being worked on currently.

    If this is your case, the solution would be move the APIM to another resource group or create the APIM in another resource group.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful