SDK & code generation

x-codeSamples

`x-codeSamples` appears on operations. Its value is a list. Used by 136 providers across 395 OpenAPI documents. Observed values include `true`, `*ref_0`, `*ref_1`, `false`. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.

SDK & code generation 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.

11430 occurrences

395 documents

136 providers

purpose-named

Where it appears

Location in the document	Occurrences
operation	11417
requestBody	2
root	7
path	2
tag	2

What its value looks like

Value shape	Occurrences
array	11343
object	73
boolean	7
string	6
empty	1

Observed values

Sampled from the specifications, most frequent first.

true*ref_0*ref_1false&ref_0&ref_1

Providers publishing it

Showing 50 of 136.

accrue-savings adanos-market-sentiment-api adobe-suite affise altruistiq anrok apideck appcharge appdirect appen augustus ava-labs bitvavo blockfrost bonitasoft bootic boxc brandfolder bulksms california-privacy-protection-agency canoe-intelligence cardano ccpa cerebras-systems citi clari cloudbees cognition-labs colissimo confluent confluent-the-data-streaming-platform contabo contextdev controlup cove.tool cpanel crypto-com cube-planning cubesoftware curated-for-you dailypay digital-ocean dmarket dolby dropbox dwolla elk-stack exa-ai finix finix-payments

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 sdk & code generation job.