OpenAPI Specification

https://spec.openapis.org/oas/v3.2.0.html
Admin
The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface...
Tokens:47,723
Snippets:623
Trust Score:9.9
Update:1 month ago
Show doc for...
Tokens:
Raw
### Header Object Examples

Source: https://spec.openapis.org/oas/latest.html

Examples demonstrating integer-type headers and string-type headers with pattern validation.

```yaml
X-Rate-Limit-Limit:
  description: The number of allowed requests in the current period
  schema:
    type: integer

```

```yaml
ETag:
  required: true
  schema:
    type: string
    # Note that quotation marks are part of the
    # ETag value, unlike many other headers that
    # use a quoted string purely for managing
    # reserved characters.
    pattern: ^"
  example: '"xyzzy"'

```

--------------------------------

### Paths Object Example

Source: https://spec.openapis.org/oas/latest.html

A basic example of a Paths Object defining a GET operation for retrieving a list of pets.

```yaml
/pets:
  get:
    description: Returns all pets from the system that the user has access to
    responses:
      '200':
        description: A list of pets.
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/pet'
```

--------------------------------

### Reference Object Examples

Source: https://spec.openapis.org/oas/latest.html

Examples of internal and external references using the $ref keyword.

```yaml
$ref: '#/components/schemas/Pet'

```

```yaml
$ref: Pet.yaml

```

```yaml
$ref: definitions.yaml#/Pet

```

--------------------------------

### Path Item Object Example

Source: https://spec.openapis.org/oas/latest.html

Demonstrates a Path Item Object containing a GET operation, shared parameters, and an additional COPY operation.

```yaml
get:
  description: Returns pets based on ID
  summary: Find pets by ID
  operationId: getPetsById
  responses:
    '200':
      description: pet response
      content:
        '*/*':
          schema:
            type: array
            items:
              $ref: '#/components/schemas/Pet'
    default:
      description: error payload
      content:
        text/html:
          schema:
            $ref: '#/components/schemas/ErrorModel'
parameters:
  - name: id
    in: path
    description: ID of pet to use
    required: true
    schema:
      type: array
      items:
        type: string
    style: simple
additionalOperations:
  COPY:
    description: Copies pet information based on ID
    summary: Copies pets by ID
    operationId: copyPetsById
    responses:
      '200':
        description: pet response
        content:
          '*/*':
            schema:
              type: array
              items:
                $ref: '#/components/schemas/Pet'
      default:
        description: error payload
        content:
          text/html:
            schema:
              $ref: '#/components/schemas/ErrorModel'
```

--------------------------------

### HTTP Request and Response Example

Source: https://spec.openapis.org/oas/latest.html

Example HTTP request and response used to demonstrate runtime expression evaluation.

```http
POST /subscribe/myevent?queryUrl=https://clientdomain.com/stillrunning HTTP/1.1
Host: example.org
Content-Type: application/json
Content-Length: 188

{
  "failedUrl": "https://clientdomain.com/failed",
  "successUrls": [
    "https://clientdomain.com/fast",
    "https://clientdomain.com/medium",
    "https://clientdomain.com/slow"
  ]
}
```

```http
201 Created
Location: https://example.org/subscription/1
```

--------------------------------

### Define Model with Example

Source: https://spec.openapis.org/oas/latest.html

Include an examples field within a schema definition to provide sample data for the model.

```yaml
type: object
properties:
  id:
    type: integer
    format: int64
  name:
    type: string
required:
  - name
examples:
  - name: Puma
    id: 1

```

--------------------------------

### Path Templating Matching Examples

Source: https://spec.openapis.org/oas/latest.html

Examples demonstrating path matching precedence, invalid identical paths, and ambiguous resolution scenarios.

```text
  /pets/{petId}
  /pets/mine
```

```text
  /pets/{petId}
  /pets/{name}
```

```text
  /{entity}/me
  /books/{id}
```

--------------------------------

### HTTP Response Example for Runtime Expression Evaluation

Source: https://spec.openapis.org/oas/v3.2.0.html

The corresponding HTTP response for the provided POST request example.

```http
201 Created
Location: https://example.org/subscription/1
```

--------------------------------

### XML Output Examples for Null Handling

Source: https://spec.openapis.org/oas/v3.2.0.html

Example XML outputs demonstrating how null values and empty objects are represented.

```xml
<product>
  <description>Thing</description>
  <related xsi:nil="true" />
</product>
```

```xml
<product count="42">
  <description>Thing</description>
  <related></related>
</product>
```

--------------------------------

### Tag Object Example

Source: https://spec.openapis.org/oas/latest.html

Example of defining multiple tags with metadata including summaries, descriptions, and categorization.

```yaml
tags:
  - name: account-updates
    summary: Account Updates
    description: Account update operations
    kind: nav

  - name: partner
    summary: Partner
    description: Operations available to the partners network
    parent: external
    kind: audience

  - name: external
    summary: External
    description: Operations available to external consumers
    kind: audience

```

--------------------------------

### Retrieval URI Resolution Example

Source: https://spec.openapis.org/oas/latest.html

Examples showing how relative references are resolved against the document's retrieval URI.

```yaml
openapi: 3.2.0
info:
  title: Example API
  version: 1.0
components:
  requestBodies:
    Foo:
      content:
        application/json:
          schema:
            $ref: schemas/foo
```

```json
{
  "type": "object",
  "properties": {
    "bar": {
      "type": "string"
    }
  }
}
```

--------------------------------

### External Documentation Object Example

Source: https://spec.openapis.org/oas/latest.html

Example of an External Documentation Object providing a description and a URL.

```yaml
description: Find more info here
url: https://example.com
```

--------------------------------

### Define Example Objects for JSON

Source: https://spec.openapis.org/oas/latest.html

Demonstrates using dataValue and serializedValue within an Example Object for JSON content.

```yaml
content:
  application/json:
    schema:
      type: object
      required:
      - author
      - title
      properties:
        author:
          type: string
        title:
          type: string
        rating:
          type: number
          minimum: 1
          maximum: 5
          multipleOf: 0.5
    examples:
      noRating:
        summary: A not-yet-rated work
        dataValue:
          author: A. Writer
          title: The Newest Book
      withRating:
        summary: A work with an average rating of 4.5 stars
        dataValue:
          author: A. Writer
          title: An Older Book
          rating: 4.5
        serializedValue: |
          {
            "author": "A. Writer",
            "title": "An Older Book",
            "rating": 4.5
          }
```

--------------------------------

### Inheritance Payload Examples

Source: https://spec.openapis.org/oas/latest.html

Example payloads demonstrating schema resolution via discriminator in an inheritance context.

```json
{
  "petType": "Cat",
  "name": "Misty"
}
```

```json
{
  "petType": "dog",
  "bark": "soft"
}
```

--------------------------------

### Define a Request Body with Referenced Schemas and External Examples

Source: https://spec.openapis.org/oas/latest.html

Demonstrates how to define a request body supporting multiple media types, each referencing a schema and providing external example values.

```yaml
description: user to add to the system
content:
  application/json:
    schema:
      $ref: '#/components/schemas/User'
    examples:
      user:
        summary: User example
        externalValue: https://foo.bar/examples/user-example.json
  application/xml:
    schema:
      $ref: '#/components/schemas/User'
    examples:
      user:
        summary: User example in XML
        externalValue: https://foo.bar/examples/user-example.xml
  text/plain:
    examples:
      user:
        summary: User example in plain text
        externalValue: https://foo.bar/examples/user-example.txt
  '*/*':
    examples:
      user:
        summary: User example in other format
        externalValue: https://foo.bar/examples/user-example.whatever
```

--------------------------------

### Components Object Definition Example

Source: https://spec.openapis.org/oas/latest.html

A comprehensive example showing the structure of a components object containing schemas, parameters, responses, and security schemes.

```yaml
components:
  schemas:
    GeneralError:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
    Category:
      type: object
      properties:
        id:
          type: integer
          format: int64
        name:
          type: string
    Tag:
      type: object
      properties:
        id:
          type: integer
          format: int64
        name:
          type: string
  parameters:
    skipParam:
      name: skip
      in: query
      description: number of items to skip
      required: true
      schema:
        type: integer
        format: int32
    limitParam:
      name: limit
      in: query
      description: max records to return
      required: true
      schema:
        type: integer
        format: int32
  responses:
    NotFound:
      description: Entity not found.
    IllegalInput:
      description: Illegal input for operation.
    GeneralError:
      description: General Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/GeneralError'
  securitySchemes:
    api_key:
      type: apiKey
      name: api-key
      in: header
    petstore_auth:
      type: oauth2
      flows:
        implicit:
          authorizationUrl: https://example.org/api/oauth/dialog
          scopes:
            write:pets: modify pets in your account
            read:pets: read your pets
```

--------------------------------

### Define JSON examples using YAML syntax

Source: https://spec.openapis.org/oas/latest.html

Uses YAML structure for the example value field, which is natively supported by the OpenAPI specification.

```yaml
application/json:
  schema:
    $ref: '#/components/schemas/Pet'
  examples:
    cat:
      summary: An example of a cat
      value:
        name: Fluffy
        petType: Cat
        color: White
        gender: male
        breed: Persian
    dog:
      summary: An example of a dog with a cat's name
      value:
        name: Puma
        petType: Dog
        color: Black
        gender: Female
        breed: Mixed
    frog:
      $ref: '#/components/examples/frog-example'
```

--------------------------------

### XML No-Null Value Example Output

Source: https://spec.openapis.org/oas/latest.html

Example XML output demonstrating the representation of an empty object.

```xml
<product count="42">
  <description>Thing</description>
  <related></related>
</product>
```

--------------------------------

### Valid Component Key Examples

Source: https://spec.openapis.org/oas/latest.html

Examples of valid keys for objects within the Components Object, which must match the regex ^[a-zA-Z0-9\.\-_]+$.

```text
User
User_1
User_Name
user-name
my.org.User
```

--------------------------------

### Define JSON examples using JSON syntax

Source: https://spec.openapis.org/oas/latest.html

Uses explicit JSON syntax for the example value field within a YAML document.

```yaml
application/json:
  schema:
    $ref: '#/components/schemas/Pet'
  examples:
    cat:
      summary: An example of a cat
      value: {
        "name": "Fluffy",
        "petType": "Cat",
        "color": "White",
        "gender": "male",
        "breed": "Persian"
      }
    dog:
      summary: An example of a dog with a cat's name
      value: {
        "name": "Puma",
        "petType": "Dog",
        "color": "Black",
        "gender": "Female",
        "breed": "Mixed"
      }
    frog:
      $ref: '#/components/examples/frog-example'
```

--------------------------------

### Querystring parameter with application/jsonpath

Source: https://spec.openapis.org/oas/latest.html

Demonstrates using JSONPath for a querystring parameter with shorthand example syntax.

```yaml
in: querystring
name: selector
content:
  application/jsonpath:
    schema:
      type: string
    example: $.a.b[1:1]
examples:
  Selector:
    serializedValue: "%24.a.b%5B1%3A1%5D"
```

--------------------------------

### Server Variables Configuration Example

Source: https://spec.openapis.org/oas/latest.html

Uses variables within the server URL template to allow dynamic host and path configuration.

```yaml
servers:
  - url: https://{username}.gigantic-server.com:{port}/{basePath}
    description: The production API server
    name: prod
    variables:
      username:
        # note! no enum here means it is an open value
        default: demo
        description: A user-specific subdomain. Use `demo` for a free sandbox environment.
      port:
        enum:
          - '8443'
          - '443'
        default: '8443'
      basePath:
        # open meaning there is the opportunity to use special base paths as assigned by the provider, default is "v2"
        default: v2

```

--------------------------------

### Define Binary Example Object

Source: https://spec.openapis.org/oas/latest.html

Uses externalValue to reference binary data files.

```yaml
content:
  image/png:
    schema: {}
    examples:
      Red:
        externalValue: ./examples/2-by-2-red-pixels.png
```

--------------------------------

### Define OAuth2 Flows Example

Source: https://spec.openapis.org/oas/latest.html

Example configuration for implicit and authorization code OAuth2 flows within an OpenAPI specification.

```yaml
type: oauth2
flows:
  implicit:
    authorizationUrl: https://example.com/api/oauth/dialog
    scopes:
      write:pets: modify pets in your account
      read:pets: read your pets
  authorizationCode:
    authorizationUrl: https://example.com/api/oauth/dialog
    tokenUrl: https://example.com/api/oauth/token
    scopes:
      write:pets: modify pets in your account
      read:pets: read your pets
```

--------------------------------

### Operation Object Example

Source: https://spec.openapis.org/oas/latest.html

Example of an Operation Object defining tags, parameters, request body, responses, and security requirements.

```yaml
tags:
  - pet
summary: Updates a pet in the store with form data
operationId: updatePetWithForm
parameters:
  - name: petId
    in: path
    description: ID of pet that needs to be updated
    required: true
    schema:
      type: string
requestBody:
  content:
    application/x-www-form-urlencoded:
      schema:
        type: object
        properties:
          name:
            description: Updated name of the pet
            type: string
          status:
            description: Updated status of the pet
            type: string
        required:
          - status
responses:
  '200':
    description: Pet updated.
    content:
      application/json: {}
      application/xml: {}
  '405':
    description: Method Not Allowed
    content:
      application/json: {}
      application/xml: {}
security:
  - petstore_auth:
      - write:pets
      - read:pets
```

--------------------------------

### HTTP Request Example for Runtime Expression Evaluation

Source: https://spec.openapis.org/oas/v3.2.0.html

An example HTTP POST request used to demonstrate how runtime expressions can extract data from headers, body, and query parameters.

```http
POST /subscribe/myevent?queryUrl=https://clientdomain.com/stillrunning HTTP/1.1
Host: example.org
Content-Type: application/json
Content-Length: 188

{
  "failedUrl": "https://clientdomain.com/failed",
  "successUrls": [
    "https://clientdomain.com/fast",
    "https://clientdomain.com/medium",
    "https://clientdomain.com/slow"
  ]
}
```

--------------------------------

### Single Server Object Example

Source: https://spec.openapis.org/oas/latest.html

A basic definition of a single server endpoint.

```yaml
url: https://development.gigantic-server.com/v1
description: Development server
name: dev

```

--------------------------------

### XML Null Value Example Output

Source: https://spec.openapis.org/oas/latest.html

Example XML output demonstrating the representation of null values using xsi:nil.

```xml
<product>
  <description>Thing</description>
  <related xsi:nil="true" />
</product>
```

--------------------------------

### Handle undefined values in manual templates

Source: https://spec.openapis.org/oas/v3.2.0.html

Examples of restructuring data and templates to handle empty objects correctly.

```yaml
formulas: {}
words:
- hello
- world
```

```text
?words=hello,world
```

```text
words.0: hello
words.1: world
```

```text
?words={words.0} {words.1}
```

```text
?words=hello%20world
```

--------------------------------

### Multiple Server Objects Example

Source: https://spec.openapis.org/oas/latest.html

Defines multiple server environments within the OpenAPI Object's servers field.

```yaml
servers:
  - url: https://development.gigantic-server.com/v1
    description: Development server
    name: dev
  - url: https://staging.gigantic-server.com/v1
    description: Staging server
    name: staging
  - url: https://api.gigantic-server.com/v1
    description: Production server
    name: prod

```

--------------------------------

### Responses Object Example

Source: https://spec.openapis.org/oas/latest.html

Defines a successful 200 response and a default error response.

```yaml
'200':
  description: a pet to be returned
  content:
    application/json:
      schema:
        $ref: '#/components/schemas/Pet'
default:
  description: Unexpected error
  content:
    application/json:
      schema:
        $ref: '#/components/schemas/ErrorModel'
```

--------------------------------

### Example request body string

Source: https://spec.openapis.org/oas/latest.html

A sample URL-encoded request body string to be parsed into its data form.

```text
code=1234&count=42&extra=%3Cinfo%3Eabc%3C/info%3E
```

--------------------------------

### Undefined Parameter Values

Source: https://spec.openapis.org/oas/latest.html

Example data where the formulas object is empty.

```yaml
formulas: {}
words:
- hello
- world
```

--------------------------------

### Example text/event-stream Request Body

Source: https://spec.openapis.org/oas/latest.html

A sample request body demonstrating various event types and formatting within a text/event-stream.

```text
event: addString
data: This data is formatted
data: across two lines
retry: 5

event: addInt64
data: 1234.5678
unknownField: this is ignored

: This is a comment
event: addJSON
data: {"foo": 42}
```

--------------------------------

### Define Parameter Data Values

Source: https://spec.openapis.org/oas/latest.html

Example data values for a parameter named 'color' used to demonstrate serialization.

```text
   string -> "blue"
   array -> ["blue", "black", "brown"]
   object -> { "R": 100, "G": 200, "B": 150 }
```

--------------------------------

### Define Security Schemes

Source: https://spec.openapis.org/oas/v3.2.0.html

Examples of various security scheme configurations for OpenAPI operations.

```yaml
type: http
scheme: basic
```

```yaml
type: apiKey
name: api-key
in: header
```

```yaml
type: http
scheme: bearer
bearerFormat: JWT
```

```yaml
type: mutualTLS
description: Cert must be signed by example.com CA
```

```yaml
type: oauth2
flows:
  implicit:
    authorizationUrl: https://example.com/api/oauth/dialog
    scopes:
      write:pets: modify pets in your account
      read:pets: read your pets
```

--------------------------------

### Serialized JSON String Parameter

Source: https://spec.openapis.org/oas/latest.html

Example of an id parameter serialized as application/json and then percent-encoded.

```text
id=%22f81d4fae-7dec-11d0-a765-00a0c91e6bf6%22
```

--------------------------------

### Full URL with JSONPath serialized parameter

Source: https://spec.openapis.org/oas/latest.html

Example of a complete URL incorporating a JSONPath-serialized querystring parameter.

```text
https://example.com/foo?%24.a.b%5B1%3A1%5D
```

--------------------------------

### Full URL with JSON serialized parameter

Source: https://spec.openapis.org/oas/latest.html

Example of a complete URL incorporating a JSON-serialized querystring parameter.

```text
https://example.com/foo?%7B%22numbers%22%3A%5B1%2C2%5D%2C%22flag%22%3Anull%7D
```

--------------------------------

### API Base URL Determination Example

Source: https://spec.openapis.org/oas/latest.html

Demonstrates how relative server URLs are resolved based on the retrieval URI of the OpenAPI document.

```yaml
openapi: 3.2.0
$self: https://apidescriptions.example.com/foo
info:
  title: Example API
  version: 1.0
servers:
- url: .
  description: The production API on this device
- url: ./test
  description: The test API on this device

```

--------------------------------

### Define Request Body for File Upload

Source: https://spec.openapis.org/oas/v3.2.0.html

Example of a requestBody configuration for submitting a binary file.

```yaml
requestBody:
  content:
    application/octet-stream: {}
```

--------------------------------

### Multipart/related Archive Example

Source: https://spec.openapis.org/oas/latest.html

Demonstrates an OpenAPI document encapsulated within a multipart/related archive where base URIs are derived from Content-Location headers.

```text
--boundary-example
Content-Type: application/openapi+yaml
Content-Location: https://example.com/api/openapi.yaml

openapi: 3.2.0
info:
  title: Example API
  version: 1.0
  externalDocs:
    url: docs.html
components:
  requestBodies:
    Foo:
      content:
        application/json:
          schema:
            $ref: "#/components/api/schemas/Foo"
  schemas:
    Foo:
      properties:
        bar:
          $ref: schemas/bar
--boundary-example
Content-Type: application/schema+json
Content-Location: https://example.com/api/schemas/bar

{
  "type": "string"
}
--boundary-example
Content-Type: text/html
Content-Location: https://example.com/api/docs.html

<html>
  <head>
    <title>API Documentation</title>
  </head>
  <body>
    <p>Awesome documentation goes here</p>
  </body>
</html>
--boundary-example
```

--------------------------------

### Define Multiple Form Parameters

Source: https://spec.openapis.org/oas/latest.html

Example of multiple style: "form" parameters equivalent to a single RFC6570 variable list.

```yaml
parameters:
- name: foo
  in: query
  schema:
    type: object
  explode: true
- name: bar
  in: query
  schema:
    type: string
```

--------------------------------

### OpenAPI document retrieval URI resolution

Source: https://spec.openapis.org/oas/v3.2.0.html

Example of an OpenAPI document resolved against a retrieval URI.

```yaml
openapi: 3.2.0
info:
  title: Example API
  version: 1.0
components:
  requestBodies:
    Foo:
      content:
        application/json:
          schema:
            $ref: schemas/foo
```

--------------------------------

### Define Multiple Specific Media Types

Source: https://spec.openapis.org/oas/v3.2.0.html

Example of specifying multiple allowed media types for a request body.

```yaml
# multiple, specific media types may be specified:
requestBody:
  content:
    # a binary file of type png or jpeg
    image/jpeg: {}
    image/png: {}
```

--------------------------------

### Response Object: Plain Text with Headers

Source: https://spec.openapis.org/oas/latest.html

Defines a response with a plain text body, an example value, and custom rate-limit headers.

```yaml
description: A simple string response
content:
  text/plain:
    schema:
      type: string
    example: 'whoa!'
headers:
  X-Rate-Limit-Limit:
    description: The number of allowed requests in the current period
    schema:
      type: integer
  X-Rate-Limit-Remaining:
    description: The number of remaining requests in the current period
    schema:
      type: integer
  X-Rate-Limit-Reset:
    description: The number of seconds left in the current period
    schema:
      type: integer
```

--------------------------------

### JSON Schema retrieval URI resolution

Source: https://spec.openapis.org/oas/v3.2.0.html

Example of a JSON Schema document retrieved from a specific URI.

```json
{
  "type": "object",
  "properties": {
    "bar": {
      "type": "string"
    }
  }
}
```

--------------------------------

### Define Binary File Content Types

Source: https://spec.openapis.org/oas/latest.html

Examples of defining content types for binary files and arbitrary JSON in OAS 3.x.

```yaml
# a PNG image as a binary file:
content:
  image/png: {}
```

```yaml
# an arbitrary binary file:
content:
  application/octet-stream: {}
```

```yaml
# arbitrary JSON without constraints beyond being syntactically valid:
content:
  application/json: {}
```

--------------------------------

### Define Boolean Query Parameter Example

Source: https://spec.openapis.org/oas/latest.html

Shows serialization of boolean values for query parameters using dataValue and serializedValue.

```yaml
name: flag
in: query
required: true
schema:
  type: boolean
examples:
  "true":
    dataValue: true
    serializedValue: flag=true
  "false":
    dataValue: false
    serializedValue: flag=false
```

--------------------------------

### Entry Document YAML Representation

Source: https://spec.openapis.org/oas/latest.html

Example of an entry document defining a security scheme and a path reference in YAML format.

```http
GET /api/description/openapi HTTP/1.1
Host: www.example.com
Accept: application/openapi+yaml
```

```yaml
components:
  securitySchemes:
    MySecurity:
      type: http
      scheme: bearer
      bearerFormat: JWT
paths:
  /foo:
    $ref: 'other#/components/pathItems/Foo'
```

--------------------------------

### OpenAPI Components and Request Body

Source: https://spec.openapis.org/oas/v3.2.0.html

An example of OpenAPI components defining a request body and a corresponding serialized form to be parsed.

```yaml
components:
  requestBodies:
    Form:
      content:
        application/x-www-form-urlencoded:
          schema:
            $ref: "#/components/schemas/FormData"
          encoding:
            extra:
              contentType: application/xml
  schemas:
    FormData:
      type: object
      properties:
        code:
          allOf:
          - type: [string, number]
            pattern: "1"
            minimum: 0
          - type: string
            pattern: "2"
        count:
          type: integer
        extra:
          type: object
```

```text
code=1234&count=42&extra=%3Cinfo%3Eabc%3C/info%3E
```

--------------------------------

### Configure XML attributes, prefixes, and namespaces

Source: https://spec.openapis.org/oas/latest.html

Demonstrates using nodeType: attribute and defining XML namespaces and prefixes within a schema.

```yaml
components:
  schemas:
    Person:
      type: object
      properties:
        id:
          type: integer
          format: int32
          xml:
            nodeType: attribute
        name:
          type: string
          xml:
            namespace: https://example.com/schema/sample
            prefix: sample
  requestBodies:
    Person:
      content:
        application/xml:
          schema:
            $ref: "#/components/schemas/Person"
          examples:
            Person:
              dataValue:
                id: 123
                name: example
              externalValue: ./examples/Person.xml
```

```xml
<Person id="123">
  <sample:name xmlns:sample="https://example.com/schema/sample">example</sample:name>
</Person>
```

--------------------------------

### Non-OAuth2 Security Requirement

Source: https://spec.openapis.org/oas/latest.html

Example of a security requirement using an API key with no additional scopes.

```yaml
api_key: []

```
Tokens:
Raw