liveBook · Manning

Parameter object

As explained in The Design of Web APIs, Second Edition

An OpenAPI Parameter Object describes a parameter accepted by an operation, including its name, location, description, requiredness, and schema.

An OpenAPI Parameter Object describes non-body input accepted by an operation. It records a parameter’s name, location, requiredness, and schema, making requests clearer for consumers and tools. section 6.4.3 section 6.6.1

Path and query parameters

A product lookup declares its path identifier explicitly: /products/{productReference} uses name: productReference, in: path, and required: true. A search operation can declare keywords and category with in: query; optional parameters may omit required or set it to false. section 6.4.3 section 6.6.1

Listing 17.10 Creating a group of query parameters
components: 
  parameters: 
    Pagination: 
      name: pagination      #1
      description: |            #2
        Pagination parameters (`.../?next=s00999&limit=10`) 
      in: query 
      schema: 
        type: object      #3
        properties:                           #4
          next: 
            description: Next page cursor 
            type: string 
          limit: 
            description: Number of elements per page 
            type: number

A reusable object-valued query parameter groups pagination inputs such as next and limit, while its description clarifies the serialized request format and tool-support trade-off. section 17.3.3

How The Design of Web APIs, Second Edition covers it

How deep it goes
Defines name, location, requiredness, and schema, then extends to reusable query serialization while deferring detailed data modeling.
Examples
Uses productReference paths, product search filters, and cursor-based pagination with next and limit.
What it assumes
Assumes familiarity with HTTP operations and paths, while introducing parameter locations and requiredness through examples.
What you can do after
Apply it via OpenAPI to describe request inputs and reuse grouped query parameters across operations.
How it connects
Connects HTTP operations with path parameters, query parameters, request bodies, pagination, and parameter serialization.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Design of Web APIs, Second Edition. The section links point to the parts of the book it draws on.