Updated on 2026-09-23 GMT+08:00

Querying Image Permissions

Function

The API is used to query image permissions.

Constraints

None

Calling Method

For details, see Calling APIs.

Authorization Information

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

  • If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
  • If you are using identity policy-based authorization, the following identity policy-based permissions are required.

    Action

    Access Level

    Resource Type (*: required)

    Condition Key

    Alias

    Dependencies

    swr:repo:getRepoAccess

    Read

    repo *

    -

    -

    -

URI

GET /v2/manage/namespaces/{namespace}/repos/{repository}/access

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

namespace

Yes

String

Organization name. Enter 1 to 64 characters, starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, periods (.), underscores (_), and hyphens (-) are allowed. Periods, underscores, and hyphens cannot be placed next to each other. A maximum of two consecutive underscores are allowed.

repository

Yes

String

Image repository name. The name contains 1 to 128 characters, starting and ending with a lowercase letter or digit. Only lowercase letters, digits, periods (.), slashes (/), underscores (_), and hyphens (-) are allowed. Periods, slashes, underscores, and hyphens cannot be placed next to each other. A maximum of two consecutive underscores are allowed. If the parameter value contains a slash (/), replace it with a dollar sign ($) before sending the request.

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

Content-Type

Yes

String

Message body type (format). Possible values:

application/json;charset=utf-8

application/json

X-Auth-Token

Yes

String

User token.

It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token.

Response Parameters

Status code: 200

Table 3 Response body parameters

Parameter

Type

Description

id

Integer

id

name

String

Organization name Enter 1 to 64 characters, starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, periods (.), underscores (_), and hyphens (-) are allowed. Periods, underscores, and hyphens cannot be placed next to each other. A maximum of two consecutive underscores are allowed.

self_auth

UserAuth object

Current user permission

others_auths

Array of UserAuth objects

Permissions of other users

Table 4 UserAuth

Parameter

Type

Description

user_id

String

User ID, which needs to be obtained from IAM.

user_name

String

Username, which needs to be obtained from IAM.

auth

Long

User permission. 7: Manage. 3: Write. 1: Read.

Example Requests

GET https://{endpoint}/v2/manage/amespaces/{namespace}/repos/{repository}/access

Example Responses

Status code: 200

{
  "id" : 1422,
  "name" : "group",
  "self_auth" : {
    "user_id" : "3059e6b5562241fda3fa441cca6f228b",
    "user_name" : "liugenping",
    "auth" : 7
  },
  "others_auths" : [ {
    "user_id" : "fb3f175c1fd146ab8cdae3272be6107b",
    "user_name" : "liugenping01",
    "auth" : 7
  } ]
}

Status Codes

Status Code

Description

200

The query succeeded.

400

An request error occurred.

401

The authentication failed.

404

The image does not exist.

500

An internal error occurred.

Error Codes

See Error Codes.