Skip to main content

Personal Access Tokens

Personal Access Tokens (PATs) are secure credentials that let you authenticate with the TIR AI Platform programmatically — without using your account password. Use them in API calls, CLI tools, scripts, and CI/CD pipelines.

Revocable AnytimeCI/CD ReadyPer-Integration TokensAudit Trail

Quick Start​

Why Use Personal Access Tokens?​

Security

Individual Revocation

Tokens can be revoked individually without affecting your password, other tokens, or active sessions.

Automation

No Interactive Login

Authenticate scripts, CI/CD pipelines, and API calls without requiring a browser or manual login.

Flexibility

Multiple Tokens

Generate separate tokens for different tools, environments, or machines — each independently managed.

Auditability

Named Tokens

Each token has a descriptive name so you can identify which integration it belongs to and revoke it precisely.

How to Manage Tokens​

1. Access the Tokens Page​

  • Log in to the TIR AI Platform.
  • Navigate to Security → Personal Access Tokens from the sidebar.

2. Create a Token​

  • Click Create Token.
  • Enter a descriptive name (e.g., ci-pipeline, dev-laptop, jupyter-integration).
  • Click Create.

Copy Your Token Immediately

The token value is shown only once after creation. Copy and store it securely — in a password manager or as an environment variable. You cannot retrieve it again.

3. View Active Tokens​

All tokens appear in the tokens list with their name and creation date.

4. Delete a Token​

  • Locate the token in the list.
  • Click the Delete icon next to it.
  • Confirm when prompted.

Token Revocation

Deleting a token immediately revokes its access. Any service or script using this token will no longer be able to authenticate.

Using Your Token​

  • In API Requests​

Pass your token as a Bearer header in any API call:

curl -H "Authorization: Bearer <your-token>" \
  https://api.e2enetworks.com/tir/v1/...

  • As an Environment Variable​

Set the token as an environment variable to avoid hardcoding it in your code:

export TIR_API_TOKEN="<your-token>"

Then reference it in your scripts:

import os
token = os.environ["TIR_API_TOKEN"]

Best Practices​

01

Naming & Organisation

  • Use descriptive names that reflect the token's purpose or machine (e.g., github-actions, macbook-pro)
  • Create one token per integration so revoking one does not break others
02

Storage & Secrets

  • Never commit tokens to source code or version control
  • Store tokens in environment variables or a secret manager
  • Copy the token immediately after creation — it is shown only once
03

Lifecycle Management

  • Rotate tokens regularly by deleting old ones and generating new ones
  • Revoke unused tokens immediately to minimise the attack surface