Machine-readable contracts

One OpenAPI document. Every normalized REST operation.

Download an OpenAPI 3.1 representation of all 162 source-derived Mappls API contracts, including per-operation hosts, authentication declarations, schemas, examples, lifecycle roles, maturity, and source provenance.

Download JSON Browse human reference

162operations

One entry for every normalized contract.

7families

Grouped into coherent source families.

67source files

Fingerprinted contract evidence.

3.1OpenAPI

Standard JSON for modern tooling.

Interoperability surface

Useful to tools. Honest about provenance.

The export is generated from the same contract catalog as the portal and MCP server. Vendor extensions keep evidence that ordinary OpenAPI fields cannot express.

x-mappls-contract-status: Distinguishes current-source from legacy-source evidence.
x-mappls-auth-mode: Preserves declared bearer, OAuth-bearer, or undeclared authentication.
x-mappls-state-model: Separates stateless, hybrid, and stateful behavior.
x-mappls-journey-role: Shows whether an operation reads, observes, commands, transitions, or retires state.
x-mappls-source-fingerprint: Binds the normalized operation to its exact extracted source.
x-mappls-boundary: Requires host, entitlement, region, quota, and terms validation before production.

mappls-normalized-openapi.json

curl --fail --location \
  https://developer.mappls.com/openapi.json \
  --output mappls-normalized-openapi.json

# Import the file into your preferred OpenAPI 3.1 client,
# validator, gateway, code generator, or agent toolchain.

Interoperability artifact, not entitlement proof

The document intentionally includes legacy repository evidence. Use each operation's status and source fields, then validate the exact production contract with Mappls.