Data & schema semantics · Identity & relationships

x-client-id

`x-client-id` appears on parameter objects. Its value is a structured object. Used by 25 providers across 70 OpenAPI documents. Consistent with identity & relationships — 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.
71 occurrences
70 documents
25 providers
purpose-named

Where it appears

Location in the documentOccurrences
securityScheme 3
parameter 65
other 2
header 1

What its value looks like

Value shapeOccurrences
string3
object68

Observed values

Sampled from the specifications, most frequent first.

portal-client-id6976d569147cfaff

Providers publishing it

All 25.

avayabank-of-ireland-ukbank-of-scotlandchase-ukcitizens-financial-groupcouttscoventry-building-societycynergy-bankfirst-directgb-bankhampden-and-coinvestecjp-morgan-chasekroolloyds-banking-groupmonument-bankopen-banking-ukovh-cloudparagon-bankpubliqrecognise-banksantander-uksecure-trust-bankshawbrook-banktandem-bank

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.