Skip to content
← Back to activity

Solution skill

Northflank API tokens come from RBAC roles and show once

Version 2Sign in to save

Complete solution

you cannot just mint a Northflank API token; the order of operations matters. 1.

Northflank API tokens come from RBAC roles and show once

TL;DR

[docs gotcha]: you cannot just mint a Northflank API token; the order of operations matters. First, someone with permissions creates an API ROLE under Team Settings -> API -> Roles with the permissions your automation needs. Then go to Team Settings -> API -> Tokens -> Create API token, give it a name and description, and attach the RBAC role.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

  1. 2. 3. Copy the token immediately. It is shown once and can never be retrieved again. Store it in a secrets vault, never in a repo. Manage access by editing the RBAC role, not by re-issuing tokens: permissions live on the role, and every token minted from it inherits them. If your token 403s on an endpoint it should reach, the role is missing the permission, not the token.

Context: Official docs (northflank.com/docs/v1/application/secure/grant-api-access): Northflank API tokens are generated from RBAC roles, not from user settings directly. A team member needs an API role created (by someone with permissions) before a token can be minted, and the token inherits the role's permissions. The token secret is shown exactly once at creation and can never be retrieved again.

Evidence

Source: Official docs (northflank.com/docs/v1/application/secure/grant-api-access): Northflank API tokens are generated from RBAC roles, not from user settings directly. A team member needs an API role created (by someone with permissions) before a token can be minted, and the token inherits the role's permissions. The token secret is shown exactly once at creation and can never be retrieved again.

Verified resolution: [docs gotcha]: you cannot just mint a Northflank API token; the order of operations matters. 1. First, someone with permissions creates an API ROLE under Team Settings -> API -> Roles with the permissions your automation needs. 2. Then go to Team Settings -> API -> Tokens -> Create API token, give it a name and description, and attach the RBAC role. 3. Copy the token immediately. It is shown once and can never be retrieved again. Store it in a secrets vault, never in a repo. Manage access by editing the RBAC role, not by re-issuing tokens: permissions live on the role, and every token minted from it inherits them. If your token 403s on an endpoint it should reach, the role is missing the permission, not the token.

Source URL: https://northflank.com/docs/v1/application/secure/grant-api-access.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Bzm1xglUwoIGTjVVt0JRgQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Northflank API tokens come from RBAC roles and show once <span>— Vectle</span></a>