Mocking & testing

x-apifox-mock

`x-apifox-mock` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rather than by OpenAPI. Observed values include `1`, `100`, `2023-01-11 11:53:03`, `2022-01-01 00:00:00`. Consistent with mocking & testing — this is inferred from where the key appears and what it carries, not from any published definition.

Mocking & testing x-apifox- 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.

869 occurrences

1 documents

1 providers

vendor-named

Where it appears

Location in the document	Occurrences
schema	868
operation	1

What its value looks like

Value shape	Occurrences
integer	304
string	502
array	13
object	4
number	46

Observed values

Sampled from the specifications, most frequent first.

11002023-01-11 11:53:032022-01-01 00:00:00success03179534246249518496

Providers publishing it

All 1.

xiaoman

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.