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
| Contract | Collection | Notes |
|---|---|---|
| Authentication | Download | Download 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. |
| API | Download | Includes process creation (POST) and GET process. |
Setup
- Download the collection for the contract you're integrating.
- Import it in Postman:
File > Import > Upload Files. - Configure credentials depending on the collection:
Authentication — open the collection, go to the Variables tab, and fill in:
| Variable | Value |
|---|---|
service_account | Your service account name. |
tenant_id | Your tenant ID. |
secret_key | Your private key (PEM format). |
base_path | Token endpoint host. Defaults to UAT (https://identityhomolog.acesso.io); change to https://identity.acesso.io for production. |
API — open each request and replace the Authorization: Bearer and APIKEY header values with your own credentials.
- 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, andbase_pathfrom 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 API collection has no pre-request script — credentials are set directly in the request headers.
What's next
- Authentication — generate the credentials the collection needs.
- API Overview — context for the API collection.