Postman
Askel connects to your customer's Postman workspace, letting your product manage API collections, update environments, and read monitor results in the API development tooling their engineers already use.
What you can do
Create and update collections
Use the Postman collections endpoint to create a new collection or update an existing one with new requests, folders, and example responses.
Read and update environments
Fetch environment variables from a named environment and update values such as base URLs, API keys, and tenant identifiers when they change in your product.
Fork and merge collections
Fork an existing collection to a target workspace using the fork endpoint, useful for distributing a template collection to multiple customer workspaces.
Read monitor results
Fetch the latest run results from a Postman monitor to check whether scheduled API health tests are passing in the customer's environment.
List workspaces and collections
Enumerate workspaces and collections accessible to the API key so your product can locate the right target without requiring the customer to copy internal IDs.
Share collections via links
Generate a shareable collection link using the collection access endpoint so customers can import your published API spec into their Postman in one click.
Updating environment variables when a customer rotates their API credentials
You sell a developer platform with API keys that customers use to authenticate calls. Wavecrest Engineering stores their integration credentials as Postman environment variables. When they rotate their API key in your product, the Postman environment should update automatically so their team's tests keep passing.
- 1
Generate a Postman API key
Wavecrest's admin navigates to postman.com, opens Account Settings, then API Keys, creates a new key, and pastes it into your product's integration settings.
- 2
Identify the environment
Askel calls the Postman environments endpoint to list Wavecrest's environments. Your onboarding team picks the Production env as the target and stores its environment ID.
- 3
Detect the key rotation
When Wavecrest rotates their API key in your product, your product triggers the Update Postman Environment workflow, passing the new key value.
- 4
Update the environment variable
Askel PATCHes the Postman environment, updating the API_KEY variable value to the new key. Other variables in the environment are left unchanged.
- 5
Confirm and notify
Askel confirms the update succeeded. Your product optionally sends Wavecrest's developer lead a Slack or email notification that the Postman environment has been refreshed.
API token
The customer's Postman user navigates to Account Settings, then API Keys at postman.com, and creates a new API key. Askel stores the key securely and uses it for all Postman API calls. API keys are scoped to the generating user's permissions and can be revoked from the same settings page.
How Askel sits between your product and the customer's system
FAQ for Postman
Which Postman plans include API access?+
Can we publish a collection to multiple customer workspaces?+
Are environment variable values returned in plaintext?+
What happens if the customer deletes the target environment?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.