Skip to main content
DELETE
Remove a resource from 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
resourceType
enum<string>
required

Kind of resource. Kind of resource a cost center or tag can be attached to.

Available options:
POD,
CLUSTER,
SERVERLESS_ENDPOINT,
NETWORK_VOLUME
resourceId
string
required

Resource identifier.

Minimum string length: 1

Response

Removed. Response has no body.

Last modified on November 3, 2026