Azure API management can truncate your operation ID and mess your next upload!

Azure API management is without any doubt a great tool to manage your APIs catalog but you can have some surprise about undocumented restrictions. Issue demonstration Let’s take a real quick example. Try to create a new API and upload this OpenAPI specification: openapi: 3.0.1 info: title: My super API version: 1.0.0 paths: /contracts/[contractId]/versions/[versionNumber]/administration/contact-informations: get: responses: 200: description: Valid response content: {} /contracts/[contractId]/versions/[versionNumber]/administration/contact-informations/[contactId]: get: responses: 200: description: Valid response content: {} The initial upload should be successful.

Read full post