Data & schema semantics · Units & formatting

x-timestamp

`x-timestamp` appears in the info block and on operations. Its value is a string. Used by 2 providers across 7 OpenAPI documents. Observed values include `2023-05-30T15:27:20Z`, `2023-05-30T15:27:19Z`, `{timestamp}`, `2026-04-01T12:00:00.0000000Z`. Consistent with units & formatting — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
9 occurrences
7 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 5
operation 4

What its value looks like

Value shapeOccurrences
string9

Observed values

Sampled from the specifications, most frequent first.

2023-05-30T15:27:20Z2023-05-30T15:27:19Z{timestamp}2026-04-01T12:00:00.0000000Z2022-05-03T09:24:07Z

Providers publishing it

All 2.

adyensinch

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the data & schema semantics job.