Mocking & testing

x-ads_command_line_example

`x-ads_command_line_example` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `curl -v "https://developer.api.autodesk.com/oss/v2/buckets" -X GET -H "Authoriza`, `curl -v ''https://developer.api.autodesk.com/oss/v2/buckets/bucketexamplekey/obj`, `curl -v ''https://developer.api.autodesk.com/oss/v2/buckets/apptestbucket/object`, `curl -v "https://developer.api.autodesk.com/oss/v2/buckets" -X POST -H "Content-`. Consistent with mocking & testing — this is inferred from where the key appears and what it carries, not from any published definition.

Mocking & testing 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.
13 occurrences
2 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 13

What its value looks like

Value shapeOccurrences
object1
string12

Observed values

Sampled from the specifications, most frequent first.

curl -v "https://developer.api.autodesk.com/oss/v2/buckets" -X GET -H "Authorizacurl -v ''https://developer.api.autodesk.com/oss/v2/buckets/bucketexamplekey/objcurl -v ''https://developer.api.autodesk.com/oss/v2/buckets/apptestbucket/objectcurl -v "https://developer.api.autodesk.com/oss/v2/buckets" -X POST -H "Content-curl -v -X POST ''https://developer.api.autodesk.com/oss/v2/buckets/apptestbuckecurl -v ''https://developer.api.autodesk.com/oss/v2/signedresources/7ffc5eef-140curl -v ''https://developer.api.autodesk.com/oss/v2/signedresources/e63f23e2-248curl -v ''https://developer.api.autodesk.com/oss/v2/signedresources/322cca8f-4cb

Providers publishing it

All 1.

autodesk-fusion

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 mocking & testing job.