Skip to main content
POST
Register an ECR delegation
Required API key scope: secrets:write

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.

Body

application/json
resource
string
required

ECR resource ARN

Example:

"arn:aws:ecr:us-east-2:418399314813:repository/runpod/deployment"

name
string | null

Optional name for the delegation

Example:

"my-delegation"

Response

Delegation created

id
string
required

Delegation identifier

Example:

"deleg_abc123"

delegatorUserId
string
required

User ID that created the delegation

Example:

"user_xyz"

awsUser
string
required

AWS user/role being delegated

Example:

"123456789"

repository
string
required

ECR repository name

Example:

"runpod/deployment"

tag
string
required

ECR image tag

Example:

"latest"

awsRegion
string
required

AWS region

Example:

"us-east-2"

createdAt
string<date-time>
required

When the delegation was created

Example:

"2026-03-13T20:00:00Z"

name
string | null

Optional name for the delegation

Example:

"my-delegation"

dockerRegistryUri
string

Formatted ECR registry URI for Docker login

Example:

"123456789.dkr.ecr.us-east-2.amazonaws.com"

Last modified on November 18, 2026