Swagger 3.0 support

API Gateway supports the import of API definition files in OpenAPI 3.0 (Swagger 3.0) format with the limitations listed below. Review these limitations before importing your API definition file.

  • API Gateway supports variables in base paths and resource paths, but not in hostnames. For example, you may include this URL in the servers object: https://my-api.akamai.com/{username}, but not this one: https://{username}.akamai.com
  • API Gateway does not support WebSocket protocols (ws:// and wss://)
  • You cannot override the servers object on the path level or operation level.
  • You can only define one base path per API configuration. You can have multiple hostnames with the same base path.
  • You can only describe one API key per API configuration.
  • You can only refer to one media type (for example, application/json) in a request body definition.
  • API Gateway does not support the not keyword.
  • API Gateway does not support the explode and style properties used for parameter descriptions.
  • API Gateway does not support the nullable attribute used to specify that a parameter value may be null.