Add resources to a namespace in Passport

Beta

Resources are the API endpoints that Passport manages access to. Adding resources to a namespace makes them visible to Passport Members, who can then request access and call them using secret references instead of real credentials.

To add a resource, choose a source, review the endpoints Passport detected, create a resource group, and map secrets to vault references. You can import existing API specifications or proxy activity, paste a curl request, or enter endpoints manually.

Before adding resources, make sure the Passport Proxy is set up. The proxy must be registered before you can map secrets.

Step 1: Choose a source

From the namespace Resources tab, click Add resources and select how you want to bring endpoints into Passport. You can import a file, paste a curl request, or enter an endpoint manually.

Import a file

Drag and drop a proxy activity export, API specification, or collection export. Passport detects the format and prepares its endpoints for review.

Passport supports the following file formats:

  • Proxy activity export (OTEL) — Proxy activity that’s grouped into the endpoints it discovered. Accepts .json, .jsonl, .ndjson, and .log files.
  • API specification — An OpenAPI or compatible specification. Accepts .json, .yaml, and .yml files.
  • Postman collection — Requests from the collection, prepared as endpoints for review. Accepts .json files.

Paste a curl request

Passport detects the host, method, path, and credential-bearing headers from the request. Enter the curl request and click Import cURL.

You can also click Use sample cURL to use a sample request for testing.

Enter an endpoint manually

Click Enter endpoint manually to define the endpoint yourself.

Step 2: Add/review endpoints

Review the endpoints Passport detected and select the ones you want to add.

  • File or curl import — Select the endpoints to include, then click Continue to group details.
  • Manual entry — Fill in the following fields, then click Add manual endpoint:
    • Resources host — The hostname of the API.
    • HTTP method — Select from the dropdown.
    • Path — The endpoint path.
    • Auth header label (optional) — The authentication header label.

Step 3: Create a resource group

Enter a name and description for the resource group, then click Next. Resource groups organize related endpoints within a namespace.

Step 4: Map secrets

Map secrets for each endpoint by selecting an existing vault reference or creating a new one. You can also skip this step and map secrets later from the namespace’s Vault tab.

To create a vault reference, do the following:

  1. Click Create vault reference.
  2. Enter a reference pointer.
  3. Select a vault type: Hashicorp (HashiCorp Vault), AWS (AWS Secrets Manager), or GCP (Google Cloud Secret Manager).
  4. Enter the vault key.
  5. Click Save vault reference.

Step 5: Create resources

Click Create resources to finish. The resource group appears in the namespace Resources tab.

Manage vault references

The Vault tab shows all vault references, which namespaces they’re used in, and the reference pointer.

To create a vault reference, do the following:

  1. Select the namespace and click the Vault tab.
  2. Click Create vault reference.
  3. Enter a reference pointer.
  4. Select a vault type: Hashicorp (HashiCorp Vault), AWS (AWS Secrets Manager), or GCP (Google Cloud Secret Manager).
  5. Enter the vault key.
  6. Click Create reference.

Next steps

With resources added, invite your team members so they can request access. Once members are added, you can manage their API access requests.