Importable API workspace

Take the complete Mappls contract atlas into Postman.

Import all 162 normalized REST operations as a portable collection, grouped by product family and paired with a credential-empty secret environment. Every request retains its source status, state model, lifecycle role, and SHA-256 provenance.

Download collection Download empty environment

162requests

Every normalized operation, exactly once.

7folders

Grouped by contract family.

12source hosts

Named variables with entitlement warnings.

0credential values

Secrets remain empty by construction.

Six-step import

From download to a safe first request.

The collection is executable scaffolding, not a promise that every operation is enabled for the importing account.

Download both artifacts

The collection contains requests and source provenance. The separate environment declares four credential slots with empty values.

Import into Postman

Import the v2.1 JSON collection and environment. Select the Mappls credential-empty environment for the workspace.

Confirm the contract generation

Each request states whether its source is current or legacy and whether authentication is bearer-based or undeclared in source evidence.

Set only issued credentials

Populate the minimum variable your entitled operation requires. Keep the environment private and disable unused OAuth fields.

Choose optional parameters

Required inputs are enabled with source-derived examples; optional query parameters are preserved but disabled until selected deliberately.

Send, inspect, and retain provenance

Correlate provider request IDs and timestamps without exporting tokens or sensitive response bodies. Validate region, quota, and terms before automation.

Mappls Postman workspace

curl --fail --location \
  https://developer.mappls.com/postman/collection.json \
  --output mappls-normalized.postman_collection.json

curl --fail --location \
  https://developer.mappls.com/postman/environment.json \
  --output mappls-empty.postman_environment.json

# Import both files. Populate credentials only in your private,
# local environment—never in the collection or source control.

Secrets belong in a private environment

Base URLs are non-secret collection variables. Bearer tokens, REST keys, client IDs, and client secrets exist only as empty environment slots. Never commit or synchronize a populated export.

Format choice

Portable v2.1 JSON, ready for the v3 path.

The collection uses Postman Collection v2.1 because it remains the stable single-file import/export format and works with Newman. Postman v12 uses its multi-file v3 format and provides a CLI migration command when a repository-native v3 workspace is preferred.

Postman schema guidance Postman CLI migration guidance