Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- Service Overview
- Billing
- Getting Started
-
User Guide
- Before You Start
- Permissions Management
- Enabling KooDrive
- Creating an Organization and Configuring KooDrive
- KooDrive Services
- Auditing
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Department Management
- User Management
-
Space Management
- Listing Departments Spaces
- Querying Space Information
- Creating a Space for a Department or Individual
- Modifying Space Information
- Deleting a Space
- Querying Space Details by Space ID
- Querying Information About a Team Space
- Creating a Group Space
- Dismissing a Team Space
- Listing Group Spaces in an Enterprise
- Listing User Spaces
- Obtains space information.
- Group Management
- Session Management
- Service Subscription
- Enterprise Settings
- Other APIs
-
Permissions Templates
- Creating a Permissions Template
- Editing a Permissions Template
- Modifying the Status of Permissions Templates
- Deleting Permissions Templates in Batches
- Querying Permissions Template Details Based on the Permissions Template ID Array
- Listing Permissions Templates by Condition
- Adding or Modifying the Association Relationship of the Initial Member Permissions
- Querying Whether a Permissions Template Is Used
- File Moderation
- Cloud Decompression
- Batch Task Operations
- Basic Task Operations
- File List Query
-
File Management
- Obtaining File Details
- Adding a File Directory
- Creating File Metadata
- Obtains the upload link.
- Checking Whether File Upload Is Completed
- Obtaining Download Links
- Renaming a File
- Clearing the Recycle Bin
- Retrieving Files Using Search Engine Capabilities
- Collecting Folder Statistics
- Obtaining the Full Name and ID Paths of a File
- File Favorites
- Sharing Management - Shared by You
- Sharing Management - Shared with You
- Sharing Management - Access Links
- Collaboration Portal
- Message Notifications
- Refined Authorization
- Appendixes
-
FAQs
- KooDrive Organizational Structure
- KooDrive Login
- KooDrive Purchase and Upgrade
- KooDrive Billing and Unsubscription
- KooDrive User Group and Member Management
-
KooDrive File Upload and Download
- Can I Upload and Download KooDrive Files in Batches?
- Is There a Limit on the Number or Size of KooDrive Files to be Uploaded in Batches?
- How Large a File Can I Upload in KooDrive?
- Why Are File Download Rates of KooDrive Different?
- Will the KooDrive Upload Task Be Canceled If I Refresh the Page?
- Will the File Transfer Window Automatically Disappear During File Upload in KooDrive?
- What Is the KooDrive File Upload Rate? How Is Upstream Traffic Billed?
- KooDrive File Deletion and Restoration
-
KooDrive File Sharing
- Can I Share KooDrive Files (Folders) with Myself?
- What Files (Folders) Are Displayed on the Shared with Me Tab Page?
- How Many KooDrive Files (Folders) Can I Share at Most Each Time?
- How Many KooDrive Records Can I Cancel for Sharing or Remove from Sharing Each Time?
- Why Is the Sharing Status Displayed as "File deleted" in KooDrive?
- Why Is the Sharing Status Displayed as "Invalid" in KooDrive?
- KooDrive Favorites
- Space Management
- General Reference
Copied.
Making an API Request
This section describes the structure of a REST API request, and uses the KooDrive API for processing files as an example to demonstrate how to call an API.
Request URI
A request URI is in the following format:
{URI-scheme}://{Endpoint}/{resource-path}?{query-string}
Although a request URI is included in the request header, most programming languages or frameworks require the request URI to be transmitted separately.
Parameter |
Description |
---|---|
URI-scheme |
Protocol used to transmit requests. All KooDrive APIs use HTTPS. |
Endpoint |
Domain name or IP address of the server bearing the REST service. The endpoint varies between services in different regions. Currently, KooDrive is deployed only in the AP-Singapore region, and the endpoint is intl.myhuaweicloud-koodrive.com. |
resource-path |
Access path of an API. Obtain the path from the URI of an API. For example, the resource-path of the API used to create a batch task is /koodrive/ose/v1/jobs. |
query-string |
This optional parameter is used to query the data of a parameter. Ensure that a question mark (?) is included before each query parameter that is in the format of Parameter name=Parameter value. For example, ?limit=10 indicates that a maximum of 10 data records will be displayed. |
For example, to create a batch task in the AP-Singapore region, obtain the endpoint of KooDrive (intl.myhuaweicloud-koodrive.com) for this region and the resource-path (/koodrive/ose/v1/jobs) in the URI of the API used to create a batch task. Then, construct the URI as follows:
https://intl.myhuaweicloud-koodrive.com/koodrive/ose/v1/jobs
Request Methods
The HTTP protocol defines the following request methods that can be used to send a request to the server:
Method |
Description |
---|---|
GET |
Request the server to return specified resources. |
POST |
Request the server to add resources or perform special operations. |
DELETE |
Request the server to delete specified resources, for example, an object. |
PUT |
Request the server to update specified resources. |
For example, in the case of the API used to create a batch task, the request method is POST. The request is as follows:
POST https://intl.myhuaweicloud-koodrive.com/koodrive/ose/v1/jobs
Request Header
- Content-Type: (optional) request body type or format. The default value is application/json. Other values of this field will be provided for specific APIs if any.
- Authorization: authentication.
Request header example:
POST https://intl.myhuaweicloud-koodrive.com/koodrive/ose/v1/jobs Content-Type: application/json Authorization: xxx
Request Body
The body of a request is often sent in a structured format as specified in the Content-Type header field. The request body transfers content except the request header.
The request body varies between APIs. Some APIs do not require the request body, such as the APIs requested using the GET and DELETE methods.
For the API used to process files, an example of the request body is as follows:
{ "taskType":1 "actionType":101 "dstContainerId": IAADfsBFCO6WtAtuA315074383680425b8aa9a130cba2d4 "taskInfo": { "srcContainerId": "IAADfsBFCO6WtAtuA315074383680425b8aa9a130cba2d4" "newFilePath": "Fm9UdqBNTAQDos6l1xPlFnIqXJg2-UdqA" "fileInfo": [ { "fileId": "FuZmQ66CF0DdpKRG1Y29Iwajbq04Nhwu3" } ] } }
If all data required for the API request is available, you can send the request to call the API through curl, Postman, or coding.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot