Why use Postman with the Portal.io API
Portal.io’s HMAC authentication means every request needs five headers and a correctly assembled signature. Getting any piece wrong produces a401 with no detail about what failed. Postman eliminates that friction during development:
- Pre-built requests — every Portal.io API endpoint is already set up with the right method, URL, headers, and sample body. You just fill in your credentials.
- Automatic HMAC signing — the collection’s pre-request script builds the canonical message and computes the Base64-encoded HMAC-SHA256 signature on every send. No manual signature work needed.
- Instant feedback — see the full response (status, headers, JSON body) immediately. Compare what you expect with what the API actually returns.
- Environment variables — store your Application Key, Secret Key, and User Key once, and they apply to every request in the collection.
Get the collection
Run in Postman
Import the Portal.io API collection directly into your Postman workspace.
Set up your environment
After importing the collection, create a Postman environment with the following variables. These are referenced by the collection’s pre-request script and request templates.| Variable | Value | Where to get it |
|---|---|---|
appId | Your API Application Key | Provided by your Portal.io representative |
secretKey | Your Secret Key | Provided by your Portal.io representative |
userKey | Your User API Key | Returned by the credential exchange endpoint (see quickstart) |
baseUrl | https://sandbox.api.portal.io | Use https://api.portal.io for production |
Make your first request
Once your environment variables are set:- Select the List Proposals request from the collection sidebar.
- Confirm the environment dropdown (top right) is set to the environment you just created.
- Click Send.
200 response with a JSON body containing your proposals array. If you get a 401, double-check that your appId, secretKey, and userKey variables are set correctly and that you selected the right environment.
Tips for working with the collection
- Duplicate before customizing. If you want to modify a request (add query parameters, change the body), duplicate it first so the original stays intact for reference.
- Check the console. Open the Postman Console (View → Show Postman Console) to see the exact request that was sent, including the computed signature. This is invaluable when debugging authentication issues.
- Switch environments for production. Create a second environment with your production credentials and
baseUrlset tohttps://api.portal.io. Switching between sandbox and production is a single dropdown change.