Skip to main content

​
Overview

nOps uses your Fastly API token to pull CDN cost and usage into Inform. The token is stored securely, validated before save, and is not shown again after you connect.

​
Prerequisites

  • A Fastly account with permission to create API tokens
  • A token with global:read scope (required for billing and usage data)
  • nOps organization administrator access
Only admins and owners can connect, re-validate, or disconnect. Members see Admin Only on connectable cards.

​
Create a Fastly API token

  1. Sign in to the Fastly control panel.
  2. Go to Account → Personal API tokens (or Account → API tokens).
  3. Click Create Token.
  4. Configure the token:
    • Name — for example nOps-Cost-Integration
    • Type — Automation token (if available)
    • Role — Billing (if prompted)
    • Scope — Read-only access (global:read)
    • Access — All Services for full cost visibility
    • Expiration — per your security policy (rotate before expiry if set)
  5. Copy the token immediately — it is typically shown only once.
The token must have global:read for nOps to retrieve billing and usage data. nOps can confirm the token itself is valid without this scope, but cost data will not sync until the token has global:read.

​
Connect in nOps

​
Where to open Fastly

  • To connect for the first time — go to Settings → Integrations (/settings/integrations or View all) and click the Fastly card.
  • To manage an existing connection — go to Settings → Account Status → Connected apps and click the Fastly chip to re-validate or disconnect.

​
Connect steps

  1. Click the Fastly card or chip.
  2. Paste your API token and click Connect.
nOps validates the token with Fastly before storing it. On success, the catalog shows Integrated or Connected apps shows Connected.

​
Manage your connection

Administrators can Re-validate stored credentials or Disconnect from the same modal. Action required means the token expired or was revoked — fix the token in Fastly, then re-validate or connect again. A token that validates but lacks global:read stays Connected without producing cost data.

​
Troubleshooting

  • Invalid token — confirm no typos and that the token is still active in Fastly. A valid token without global:read will connect but cost data will not appear.
  • No data — allow up to 24 hours after connect; confirm billing activity exists in Fastly.
  • Rate limits — wait briefly and use Re-validate.

​
Security

Treat the API token like a password. Rotate on a schedule even if you chose “never expire” in Fastly.