Skip to main content

Postman Collection

Each contract ships with a Postman collection pre-configured with sandbox URLs and example request bodies. Import the collection, fill in your credentials, and you can call every endpoint without writing code.

Collections by contract

ContractCollectionNotes
AuthenticationDownloadDownload the file below, import it into Postman, and replace the values of the parameters "service_account," "tenant_id," and "secret_key" to test the request.
Web & SDKDownloadIncludes process creation, GET process, GET evidences, and GET PDF.
APIDownloadIncludes process creation (POST) and GET process.

Setup

  1. Download the collection for the contract you're integrating.
  2. Import it in Postman: File > Import > Upload Files.
  3. Configure credentials depending on the collection:

Authentication — open the collection, go to the Variables tab, and fill in:

VariableValue
service_accountYour service account name.
tenant_idYour tenant ID.
secret_keyYour private key (PEM format).
base_pathToken endpoint host. Defaults to UAT (https://identityhomolog.acesso.io); change to https://identity.acesso.io for production.

Web & SDK — open each request and replace the Authorization: Bearer value with your own access token.

API — open each request and replace the Authorization: Bearer and APIKEY header values with your own credentials.

  1. Run the Authentication request — the pre-request script automatically builds the JWT assertion and stores it in {{jwt_token}}.

Pre-request scripts

Only the Authentication collection includes a pre-request script. It:

  • Reads service_account, tenant_id, secret_key, and base_path from collection variables.
  • Builds and signs the JWT assertion (RS256) using the embedded KJUR library.
  • Saves the signed token in {{jwt_token}}, which is injected into the request body automatically.

The Web & SDK and API collections have no pre-request scripts — credentials are set directly in the request headers.

What's next