Data & schema semantics

x-postman-request

`x-postman-request` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooling rather than by OpenAPI. Observed values include `{{base_url}}/compliance/api/v3/companies/{{company_reference}}/users/{{user_id}}`, `{{base_url}}/compliance/api/v3/companies/{{company_reference}}`, `https://finditparts.com/api/v1/reseller_customer_sessions/:reseller_customer_ses`, `https://finditparts.com/api/v1/sessions`. 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.
99 occurrences
4 documents
3 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 99

What its value looks like

Value shapeOccurrences
string99

Observed values

Sampled from the specifications, most frequent first.

{{base_url}}/compliance/api/v3/companies/{{company_reference}}/users/{{user_id}}{{base_url}}/compliance/api/v3/companies/{{company_reference}}https://finditparts.com/api/v1/reseller_customer_sessions/:reseller_customer_seshttps://finditparts.com/api/v1/sessionshttps://finditparts.com/api/v1/addresses/:address_idhttps://finditparts.com/api/v1/addresseshttps://finditparts.com/api/v1/carts/:cart_id/line_itemshttps://finditparts.com/api/v1/carts/:cart_id/shipping_methods

Providers publishing it

All 3.

1kosmosfinditpartszenledger

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.