OpenAPI 3.2 generator: Sume's spec is still 3.0.3

Sume's OpenAPI document declares "openapi": "3.0.3". It is not a 3.2 document, so a generator that only reads 3.2 will not be a match, while one that reads 3.0.x will. The live schema at https://api.sume.com/reference/json is the source of truth.

Sume's side is from the Public API page and the OpenAPI file the docs serve, read 2026-09-30. The generator example is from the fastify-swagger release page.

What does the generator release say?

The fastify-swagger releases page lists v9.9.0 (2026-09-22) with the single change "OpenAPI 3.2.0 compatibility". v9.9.1 (2026-09-30) lists fixes including converting nullable values and keeping examples for OpenAPI 3.1+. The page does not say what a generator does with an older 3.0.3 document, so check your tool's docs for the versions it reads.

Which version does Sume serve?

How do I check what my tool will read?

Fetch the live document and print the version before wiring a generator into CI.

const res = await fetch("https://api.sume.com/reference/json");
const spec = await res.json();
console.log(spec.openapi); // 3.0.3 when read on 2026-09-30
console.log(Object.keys(spec.paths).length + " paths");

Do I need a generator at all?

Not for TypeScript. The docs say @sume-com/sdk wraps every operation with types generated from the same OpenAPI document, so you can skip your own generation step. For other languages, point a generator that supports 3.0.x at the live URL, and pin the output to the schema you generated from. Sume OpenAPI spec and API clients lists what is in the spec.

What if my tool insists on 3.2?

I found nothing in Sume's docs that promises a 3.2 version, so do not assume one. Keep the tool on a 3.0-capable release for Sume, or hand-write the operations you need. The schema, not this post, is the authority on field names.