Custom connector x-ms-notification-content doesn't work at operation level

Like (1) Share

Report

Posted on 14 Jun 2023 20:04:10 by rbnswartz_wa

I'm creating a custom connector that has a custom trigger. I've added x-ms-notification-content to the trigger in the operation but the custom connector validation still complains about it missing the notification content extension. If I were to move it up to the resource level and not the operation level it accepts it but I have another get operation on that same resource that it then wants a x-ms-notification-url attribute on it but there is literally no place in the get request that I can add it to because the api has no field for it. The documentation found at https://learn.microsoft.com/en-us/connectors/custom-connectors/openapi-extensions#x-ms-notification-content specifies it should be on the Operation level. Am I missing something or is the documentation wrong?