An indigo-fen catalog already has a Swagger/OpenAPI file for its permit APIs. What is the preferred way to create those operations in API Management?
Select an answer to reveal the explanation.
Short Explanation
Got OpenAPI already? Import it—don’t sit there redrawing every indigo-fen operation by hand.
Full Explanation
When an OpenAPI (Swagger) specification already describes the iris-ridge API, import that specification into API Management instead of hand-recreating every operation. Import maps paths, methods, parameters, and schemas into APIM operations quickly and keeps the gateway aligned with the contract the city already published to partners and internal teams.
Recreating each operation manually from memory or screenshots invites drift, typos, missed required headers, and incomplete request bodies when a machine-readable spec exists. Storing the OpenAPI file only in a wiki or SharePoint library documents intent for readers but never creates gateway operations, backends, or policies. Converting the specification into a Service Bus topic confuses an HTTP API description with a messaging entity and does not produce callable APIM APIs.
Exam caveat: APIM supports OpenAPI import as a first-class create path—prefer import whenever the municipal team already maintains a spec, then adjust backend URL and policies afterward rather than redrawing the whole surface.
Operational check: use Add API → OpenAPI (or the CLI/Bicep equivalent), select the iris-ridge file or URL, review the imported operations against the source spec, set the correct backend service URL, publish via a product, and call one operation through the gateway to confirm routing and status codes.