liveBook · Manning

Lower bound

As explained in API Design Patterns

A lower bound is the smallest permitted value of a numeric quantity.

A lower bound is the smallest permitted value for a quantity. For numeric API fields, choose it alongside the upper bound and zero value, because representation size and language behavior affect which values can be handled consistently. section 5.3.1

Apply lower bounds deliberately:

  • Reject values below the permitted minimum when they have no meaningful API interpretation. section 21.3.1
  • Document bounds and defaults consistently across equivalent API fields. section 21.3.1
  • Select a numeric representation that can accommodate the intended range across languages and systems. section 5.3.1

Page-size validation

A negative page size is below the meaningful lower bound and should produce an invalid-request error. A very large requested maximum can remain valid if the server returns fewer results than requested. section 21.3.1

How API Design Patterns covers it

How deep it goes
Explains bounds through storage ranges and applies lower bounds to pagination, stopping short of formal mathematical treatment.
Examples
Uses integer storage ranges, floating-point representations, and negative or oversized page-size requests.
What it assumes
Assumes basic numeric fields and API requests; teaches how minimum values interact with representation and validation.
What you can do after
Apply lower bounds to numeric API fields and pagination validation while preserving cross-system compatibility.
How it connects
Connects lower bounds with upper bounds, zero values, numeric representations, page size, and pagination.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of API Design Patterns. The section links point to the parts of the book it draws on.