Data & schema semantics

x-postman-request

`x-postman-request` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooling rather than by OpenAPI. Observed values include `https://{{tenantDNS}}/api/r1/system/community_info/fetch`, `https://{{tenantDNS}}/caas/sd`, `/document_share_session/create`, `/v3/document_share_session/result`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-postman- namespace 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.
29 occurrences
1 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 29

What its value looks like

Value shapeOccurrences
string29

Observed values

Sampled from the specifications, most frequent first.

https://{{tenantDNS}}/api/r1/system/community_info/fetchhttps://{{tenantDNS}}/caas/sd/document_share_session/create/v3/document_share_session/result{{tenantDNS}}/api/r1/community/{{community_name}}/userid/johndoe/ial{{client_api}}/reports/tenant/:tenantID/community/:communityID/events{{client_api}}/reports/tenant/:tenantID/community/:communityID/metrics{{client_api}}/reports/tenant/:tenantID/community/:communityID/application_usage

Providers publishing it

All 1.

1kosmos

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.