SoftWare Repository for Container
SoftWare Repository for Container
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Basics of Docker
-
Image Management
- Pushing an Image Through a Container Engine Client
- Obtaining a Long-Term Valid Docker Login Command
- Obtaining a Long-Term Valid containerd Pull/Push Command
- Uploading an Image Through the SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing Private Images
- Adding a Trigger
- Adding an Image Retention Policy
- Image Center
- Organization Management
- User Permissions
- Auditing
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Organization Management
- Image Repository Management
- Image Tag Management
- Shared Account Management
- API Versions
- Organization Permission Management
- Image Permission Management
- Automatic Image Synchronization Task Management
- Trigger Management
- Image Retention Policy Management
- Temporary Login Command
- Quota Management
- Example Applications
- Appendixes
- Change History
- FAQs
- Videos
- SDK Reference
On this page
Help Center/
SoftWare Repository for Container/
API Reference/
API/
Organization Management/
Querying the Details of an Organization
Querying the Details of an Organization
Updated on 2023-04-04 GMT+08:00
Function
Query the details of an organization by its name.
Response
- Response parameters
Table 2 Response body parameter description Parameter
Type
Description
id
Integer
Organization ID
name
String
Organization name
creator_name
String
IAM username
auth
Integer
User permission
- 7: Manage
- 3: Write
- 1: Read
- Example response
{ "id": 1422, "name": "group", "creator_name": "username", "auth": 7 }
Status Code
Status Code |
Description |
---|---|
200 |
Query succeeded. |
400 |
Request error. |
401 |
Authentication failed. |
404 |
The organization does not exist. |
500 |
Internal error. |
Parent topic: Organization Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.