SIGNALS Docs

API

Manage personal access tokens, API policy, and webhook retention from Admin.

Overview

The API page manages the current user’s Sanctum personal access tokens alongside application-wide API and webhook policies. Administrators with users.view can also inspect every user's token expiry and last-used time.

Where it lives

Route: /admin/settings/api (admin.settings.api)

Open Admin → Users & Security → API. The Tokens tab requires admin access. Editing and revoking tokens remain scoped to the current user. The API policy and Webhook policy tabs require settings.manage.

Key workflows

Action Behaviour
Create Token Name, ability checkboxes from AbilityRegistry, optional rate limit (1–10000 req/min)
Show once Plain-text token shown once with copy — cannot be retrieved later
Edit scopes Update abilities and rate limit without rotating the secret
Revoke Confirmation modal; deletes the token
API policy Configure authenticated and unauthenticated rate limits, token expiry, and idempotency-key requirements
Webhook policy Configure outbox retention

Abilities use resource:action keys. A token cannot exceed what the creating user may grant.

Token expiry defaults to 365 days and can be set from 0 to 3,650 days; 0 turns off policy-based expiry. The table shows each token's expiry and last-used time. Expired tokens cannot authenticate. API clients can inspect the same metadata through GET /api/v1/api-tokens and revoke their own tokens through DELETE /api/v1/api-tokens/{token}.

At a glance

Manage API tokens for programmatic access to the Signals API, API request policy, and webhook retention. Each token has a name, a set of abilities controlling which endpoints it can access, and usage tracking.

Action Description
Create Token Generate a new API token with selected abilities
Revoke Permanently delete a token

Token values are shown once at creation and cannot be retrieved later. If a token is lost, revoke it and create a new one.

Note

API tokens inherit the creating user's account permissions. A token cannot exceed the abilities granted to it.

Outbound and inbound webhooks are not managed here — they live in the API console.

Tokens issued without an explicit deadline use the current default lifetime measured from issuance. Increasing the default extends those tokens; explicit administrator-set expiries remain unchanged.