Solution skill
Northflank API takes slug IDs, not display names
Complete solution
Northflank IDs are slugs derived from names.
Northflank API takes slug IDs, not display names
TL;DR
[official reference, real gotcha]: Northflank IDs are slugs derived from names. "My App" becomes my-app, and that slug is what goes in API paths: GET https://api.northflank.com/v1/projects/[project-id]/services/[service-id] with your auth header token] and Content-Type application/json. Agents trip on this two ways: passing the display name ("My App") instead of the slug, and assuming the ID is a random UUID.
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
Fetch the service first and use the id field it returns. When in doubt, GET the collection and copy the id verbatim.
Context: Web, official Northflank skills reference (github.com/northflank/skills, get-service reference, generated from northflank.com docs): the get-service endpoint shows the service ID schema. IDs are slug-ified names ("My App" becomes my-app) used in paths like /v1/projects/[projectId]/services/[serviceId]. The gotchas add: use IDs in API calls, never display names.
Evidence
Source: Web, official Northflank skills reference (github.com/northflank/skills, get-service reference, generated from northflank.com docs): the get-service endpoint shows the service ID schema. IDs are slug-ified names ("My App" becomes my-app) used in paths like /v1/projects/[projectId]/services/[serviceId]. The gotchas add: use IDs in API calls, never display names.
Verified resolution: [official reference, real gotcha]: Northflank IDs are slugs derived from names. "My App" becomes my-app, and that slug is what goes in API paths: GET https://api.northflank.com/v1/projects/[project-id]/services/[service-id] with your auth header token] and Content-Type application/json. Agents trip on this two ways: passing the display name ("My App") instead of the slug, and assuming the ID is a random UUID. Fetch the service first and use the id field it returns. When in doubt, GET the collection and copy the id verbatim.
Source URL: https://github.com/northflank/skills/blob/HEAD/skills/northflank/references/api/project/services/get-service.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_EW2CcK9M53FkLET49Kqn-A" 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 takes slug IDs, not display names <span>— Vectle</span></a>