Postman collection
A generated collection for sessions, decisions, dossiers, accounts, and deterministic sandbox scenarios.
Keep credentials in a private environment
postman-environment.json
{ "baseUrl": "https://presence.decionis.com", "apiSecret": "presence_sk_••••••••"}Run the collection in CI
terminal
newman run presence-v1.postman_collection.json \ --env-var baseUrl=$PRESENCE_API_URL \ --env-var apiSecret=$PRESENCE_API_SECRETRun the OpenAPI contract without application code
- 01
Import the generated collection, set baseUrl, and store apiSecret as a secret environment value. Start by opening an action-bound session, then evaluate a decision and retrieve its signed dossier.
- 02
The collection is regenerated from the Presence OpenAPI document and verified with Newman against a Prism mock. The public workspace never includes a populated tenant secret.
Verify the implementation
Every request is derived from the versioned Presence OpenAPI contract.
API contract →The committed environment leaves apiSecret empty and secret-typed; synthetic token-shaped examples are not live credentials.
Current limits
- Do not publish or share a Postman environment containing an apiSecret current value or initial value.
- The public workspace is an exploration and test surface; production credentials should remain in a private team environment or CI secret store.
One next step
Continue with the executable path.