Skip to content
Try the API

Postman

Postman can build a complete collection from the Elastio OpenAPI spec, with every operation grouped by tag and its parameters filled in. You then point it at your tenant with a couple of variables.

  1. In Postman, select Import.

  2. Choose Link and paste the spec URL:

    https://developer.elastio.com/openapi/elastio-api.json

    You can also download the file and drop it into the import dialog.

  3. Import it as a Postman Collection. In the import settings, set folder organization to Tags to group requests the same way as the API reference (Incidents, Assets, Slack and so on).

Re-import from the same link when the API changes. Check the Changelog to see what’s new.

The spec’s server is https://{tenant}.app.elastio.com, so imported requests use a {{baseUrl}} variable. Open the collection, go to Variables and set:

Variable Value
tenant Your console subdomain, for example acme.
baseUrl https://{{tenant}}.app.elastio.com

If the import created baseUrl with a placeholder value such as https://your-tenant.app.elastio.com, replace it with the value above so it follows tenant.

  1. Open the collection and go to the Authorization tab.

  2. Set Auth Type to Bearer Token and enter {{elastioToken}} as the token.

  3. Leave each request’s authorization set to Inherit auth from parent so they all use it.

Create a personal access token with only the scopes you need for testing, and store it as elastioToken in an environment (below) rather than in the collection, so it isn’t shared when you export or share the collection.

If you work with more than one tenant, create a Postman environment for each and switch between them from the environment picker.

Variable Type Example
tenant default acme
elastioToken secret your personal access token

Environment values override collection values of the same name, so {{baseUrl}} picks up the tenant of the active environment. Mark elastioToken as secret so Postman masks it.

The Wiz inbound operation (POST /gateway/integration/v1/wiz/webhook) authenticates with a separate integration token instead of a personal access token. If you test it from Postman, override the authorization on that request with the integration token. See Wiz.

  • For lists that use next_page_token, copy pagination.next_page_token from the response into the request’s next_page_token query parameter, or script it in Post-response with pm.collectionVariables.set("nextPageToken", pm.response.json().pagination?.next_page_token).
  • The API reference on this site can send the same requests from the browser if you don’t want to install anything.