---
title: Postman Collection
description: Ready-to-use Postman collections for the Authentication, Web & SDK, and API contracts.
canonical: https://developer.unico.io/dual-api/developers/api-reference/postman
locale: en
generated_by: markdown-export
---

- [/](/)
- [API Reference](/dual-api/developers/api-reference/)
- Postman Collection

**On this page# 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**Authentication**[Download](/postman/oauth2.postman_collection.json)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.**Web & SDK**[Download](/postman/web-sdk-integration.postman_collection.json)Includes process creation, GET process, GET evidences, and GET PDF.**API**[Download](/postman/api-integration.postman_collection.json)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:
VariableValue`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.
**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.

**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​

[Authentication](/dual-api/developers/api-reference/authentication) — generate the credentials the collection needs.
[Web & SDK Overview](/dual-api/developers/api-reference/web-sdk) — context for the Web & SDK collection.
[API Overview](/dual-api/developers/api-reference/api) — context for the API collection.
Last updated on Oct 8, 2026**