Skip to navigation

Create a namespace from an API template

An API template is a prebuilt setup for a popular API, such as Stripe, OpenAI, or Cloudflare. When you create a namespace from a template, Passport creates the namespace, its secret references, and its resource groups and endpoints in one pass. You only enter what’s specific to your company, such as your API host and where your credentials are stored.

Use a template when the API you want to manage is in the template gallery. To bring in an API that isn’t there, create a namespace and add resources yourself.

Only Passport Admins can use templates. Passport Members don’t see the Templates page.

Before you begin

Make sure you have the following:

  • A registered Passport Proxy, so you can map secrets after the namespace exists.
  • A secret stored in your vault for each credential the template asks for. Passport stores a pointer to the secret, not its value.
  • Long-lived organization credentials for the API. Templates don’t cover personal tokens or OAuth sign-in. Some vendors also require a specific plan to issue the credential, such as an enterprise plan for service accounts.

Step 1: Choose a template

  1. In the Passport app, click Templates in the left sidebar.
  2. Find the API you want. Each card shows the API’s name, the number of endpoints and resource groups it includes, and the template version.
  3. Click the card to open the template’s setup page.

The setup page has four steps: Configure, Credentials, Review, and Create.

Step 2: Configure the namespace

  1. Enter a Namespace name.
  2. Optionally, edit the Description. It’s prefilled from the template.
  3. If the API runs on a host that’s unique to your company, enter your value under API host. Passport checks the format.
  4. Under Sign-in, review how the API authenticates. If the API supports more than one sign-in method, select the one you use.
  5. Under Resource groups, select the groups to create. All groups are selected by default. Expand a group to see its endpoints.
  6. Click Next.

Groups that can change data, delete data, or manage access are marked Sensitive. Clear the groups your team doesn’t need, especially sensitive ones, so those endpoints are never created.

Step 3: Add credentials

For each credential the template needs, create a secret reference that points to the secret in your vault:

  1. Enter a Secret Name.
  2. Select a Vault type.
  3. Enter the Vault key, which is the path to the secret in your vault.
  4. Click Next.

Some APIs need more than one credential. For example, the Anthropic template has separate keys for the Claude API and the Admin API, so each gets its own secret reference. Use a different secret for each one.

Each secret is mapped to its authentication header, and the template’s endpoints are created as active.

Step 4: Review and create the namespace

  1. On Review, check the summary of resource groups, endpoints, secret slots, and secret references to be created.
  2. Click Create namespace.

Passport creates the following, in order:

  1. The namespace.
  2. The secret references.
  3. Each resource group, followed by its endpoints.

A progress list shows each stage. Large templates can take a while because endpoints are created one at a time. When creation finishes, Passport opens the new namespace.

Recover from a failed creation

If a step fails, the page tells you what was and wasn’t created.

  • Click Retry to continue from where creation stopped. Passport doesn’t create the namespace, secret references, or groups it already created a second time.
  • Click Open namespace to leave the page and work with what was created, or Back to review if the namespace wasn’t created.

Next steps

After the namespace is created, map any remaining secrets if needed, then approve API access requests from Passport Members.