Skip to content

Postman Collection & Environment Downloads

This page hosts the signed, version-controlled artefacts that enable local or automated testing of the AnkaSecure API in Postman-compatible tooling.
Both files are regenerated on every release build and served directly from the documentation site; no external registry is required.

Artifact Description SHA-256
ankasecure-v2.postman_collection.json Postman Collection v2.1 grouping every AnkaSecure endpoint by tag, enriched with pre-request and test scripts. downloads/postman/core-generate-postman-collection.sha256
ankasecure-env.json Postman Environment declaring variables protocol, host, port, baseUrl and token, consumed by the collection at runtime. 935536adaf30e3bcf4c38cb7e2100b42ad56cd002e3e2bb33192036806c05318

Integrity – verify the checksum locally before importing; any mismatch indicates file corruption or an outdated browser cache.

Usage Workflow

  1. Download both JSON files to a secure local directory.
  2. Open Postman Desktop → File › Import → Upload Files
    – Select the collection and the environment.
  3. Activate the imported environment (upper-right selector).
  4. Authenticate using the Authentication folder in the collection; the login request stores the resulting JWT in the token variable for all subsequent calls.
  5. Run any folder or the entire collection with Postman Runner or Newman to validate contract compliance and performance baselines.

Update Policy

  • A new collection and its corresponding checksum are generated during every release build (mvn package) via the openapi-generator-maven-plugin.
  • The environment file is tracked in Git and updated only when variable semantics change (for example, the introduction of new headers).
  • Deprecated variables are retained for one full minor release cycle to preserve backward compatibility with automated pipelines.

Troubleshooting

Symptom Resolution
Requests fail with {{baseUrl}} unresolved Ensure the environment is enabled and that its variable scope is environment, not globals.
401 Unauthorized after successful login Confirm that workspace-level scripts do not override the Authorization header set by the collection.
Checksum mismatch Clear browser cache, re-download, and validate again; if the mismatch persists, contact documentation support.

Last updated: 12 May 2025