Skip to main content
GET
Get a cost center

Authorizations

Authorization
string
header
required

Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.

Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.

Path Parameters

id
string
required

Cost center identifier.

Minimum string length: 1

Response

OK

id
string
required
Example:

"clz1x9k4a0000qw3h8s7d2f1g"

value
string
required

Cost center name exactly as stored, so it matches billing breakdowns.

Example:

"team-ml"

Last modified on November 3, 2026