/
as a delimiter for each levelin the hierarchy (e.g. Apparel/Men's/T-Shirts).id
field as shown in the example below.$ref
pointers can't reference external files.x-ms-paths
and x-servers
are the only supported extensions.Recursion
- API Management doesn't support definitions defined recursively (for example, schemas referring to themselves).Produces
keyword, which describes MIME types returned by an API, isn't supported.servers
are specified, API Management will try to select the first HTTPs URL. If there aren't any HTTPs URLs - the first HTTP URL. If there aren't any HTTP URLs - the server URL will be empty.Examples
isn't supported, but example
is.operationId
and summary
respectively. operationId
value is normalized following the rules described below. summary
value is imported as-is and its length is limited to 300 characters.operationId
isn't specified (that is, not present, null
, or empty), Azure resource name value will be generated by combining HTTP method and path template, for example, get-foo
.summary
isn't specified (that is, not present, null
, or empty), display name
value will set to operationId
. If operationId
is not specified, display name value will be generated by combining HTTP method and path template, for example, Get - /foo
.operationId
value to Azure resource name of existing operation.operationId
property for every operation.operationId
after initial import.operationId
and HTTP method or path template at the same time.operationId
, and display name will be exported as a summary
.Normalization rules for operationIdGET-/foo/{bar}?buzz={quix}
will be transformed into get-foo-bar-buzz-quix-
.get-foo-bar-buzz-quix-
will become get-foo-bar-buzz-quix
-1, -2, ..., -999
.