Back to Changelog
New
Improvement

User-independent API tokens available

You can now generate standalone API tokens decoupled from individual user accounts. Your integrations no longer rely on a specific team member's profile to stay connected.

The API page (Settings -> Integrations -> REST API) has a new look and a few new features:

What's new

  • Refreshed UI: the page is cleaner, so it’s easier to find and manage your keys.

  • See who has a key: admins can see which agents have an API key.

  • Workspace-level tokens: Generate API keys tied directly to your Trengo account rather than an individual user.

  • Independent access: Tokens stay active regardless of staff departures, role changes, or permission updates.

  • Legacy keys: older API keys are now labelled as legacy. We’ll deprecate them at some point.

Why this matters

Tying mission-critical infrastructure to an employee's profile is a liability. When an admin leaves the company and their account is deactivated, integrations break and syncs silently fail. Standalone tokens keep your production pipelines stable, secure, and entirely separate from your team roster.

Like this update? Let the team know so they get even more motivated to bring more awesome updates to you.