Data & schema semantics

x-swagger-1-2-source

`x-swagger-1-2-source` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-swagger-` namespace, so its meaning is defined by swagger tooling rather than by OpenAPI. Observed values include `https://www.51offer.com/api-docs/default/ngadviser`, `https://www.51offer.com/api-docs/default/ngalliance`, `https://www.51offer.com/api-docs/default/ngmall`, `https://www.51offer.com/api-docs/default/nguserinfo`. 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-swagger- 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.
389 occurrences
1 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 389

What its value looks like

Value shapeOccurrences
string389

Observed values

Sampled from the specifications, most frequent first.

https://www.51offer.com/api-docs/default/ngadviserhttps://www.51offer.com/api-docs/default/ngalliancehttps://www.51offer.com/api-docs/default/ngmallhttps://www.51offer.com/api-docs/default/nguserinfohttps://www.51offer.com/api-docs/default/diymapplyhttps://www.51offer.com/api-docs/default/ngdiyselectschoolhttps://www.51offer.com/api-docs/default/enroll-controllerhttps://www.51offer.com/api-docs/default/ngpic

Providers publishing it

All 1.

51offer

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.