Data & schema semantics · Identity & relationships

x-apievangelist-resource-path

`x-apievangelist-resource-path` appears in the info block. Its value is a string. Used by a single provider across 59 OpenAPI documents. Observed values include `benefits/beneficiaries/v1/beneficiaries`, `benefits/dependents/v1/dependents`, `benefits/external-plans/v1/external-plans`, `hcm/applicant-onboarding/v2/applicant-onboarding`. 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.
This one is ours. API Evangelist wrote this key into its own copies of provider specifications. It is shown for completeness — the catalog is not exempt from its own inventory.
59 occurrences
59 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 59

What its value looks like

Value shapeOccurrences
string59

Observed values

Sampled from the specifications, most frequent first.

benefits/beneficiaries/v1/beneficiariesbenefits/dependents/v1/dependentsbenefits/external-plans/v1/external-planshcm/applicant-onboarding/v2/applicant-onboardinghcm/validation-tables/v1/validation-tableshcm/wfn-codelists/v3/wfn-codelistshr/corporate-directory/v1/corporate-directoryhr/hr-work-assignment-management/v3/hr-work-assignment-management

Providers publishing it

All 1.

adp

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.