> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Postman

> Connect your Postman team to Oleria to continuously discover team member access across your API development platform.

Postman is an API development platform used by engineering teams to build and test APIs. Connect your Postman team to Oleria to bring team member access into your identity and access graph, without a dedicated Postman-specific integration.

## What Oleria discovers

User accounts and profile attributes synced from your Postman team directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Postman's standard sync schedule.

## Prerequisites

* Admin access in Postman with permission to generate an API key.
* Admin access on the Oleria platform to add a new integration.

<Note>
  The exact location of these settings can change over time. If the steps below don't match what you see, refer to Postman's own API documentation.
</Note>

## Get your SCIM credentials from Postman

<Steps>
  <Step title="Generate an API key in Postman">
    Sign in to Postman as an admin, go to **Team Settings** → **Authentication**, and generate an API key.
  </Step>

  <Step title="Copy your SCIM Base URL and Authentication token">
    Copy both values before you leave the page - you'll paste them into Oleria in the next section:

    * **SCIM Base URL** - the HTTPS API endpoint for your Postman team.
    * **Authentication token** - the API key you generated.

    <Note>
      Copy the key now. Many applications display it only once. Store it securely and rotate it per your organization's security policy.
    </Note>
  </Step>
</Steps>

## Connect Postman to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations**, then select the **Postman** tile.
  </Step>

  <Step title="Complete the connection form">
    Select **Continue** and fill in the connection form:

    | Field                | Notes                                                                                  |
    | :------------------- | :------------------------------------------------------------------------------------- |
    | Instance name        | Optional. Short, recognizable label for this connection (for example, `postman-prod`). |
    | SCIM Base URL        | Required. The HTTPS API endpoint copied from Postman.                                  |
    | Authentication token | Required. The API key issued by Postman.                                               |
  </Step>

  <Step title="Save the integration">
    Select **Connect** to validate the credentials and save the integration.
  </Step>
</Steps>

## Verify the integration

Confirm the new instance appears in your Oleria workspace under **Connected Integrations** with a status of **Healthy**. Oleria syncs users from Postman on the standard SCIM provisioning schedule once the initial sync completes.

<Note>
  If Postman rotates your API key, update the Authentication token in Oleria by editing the integration.
</Note>

## Governance actions

Oleria can also invoke lifecycle actions in Postman when the key you provide has write access:

* Enable or disable a user account
* Create a new user

<Note>
  Many teams start with a read-only key for visibility, then grant write access once they're ready to automate remediation in Postman.
</Note>

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).