Before calling a Drive and Photo Service (PDS) API operation, get familiar with the endpoints, communication protocol, request method, request and response format, and encoding format.
Endpoints
PDS endpoints follow the pattern {domainID}.api.aliyunpds.com for internet access and {domainID}.api-vpc.aliyunpds.com for Virtual Private Cloud (VPC) access. VPC endpoints use the -vpc suffix. The management plane uses a separate endpoint with {regionID} as the prefix instead of {domainID}.
domainID is the domain ID and regionID is the region ID. Replace both with your actual values.
|
Network type |
Endpoint for identity authentication |
Endpoint for PDS access |
Endpoint for PDS management |
|
Internet |
{domainID}.api.aliyunpds.com |
{domainID}.api.aliyunpds.com |
{regionID}.admin.aliyunpds.com |
|
Virtual Private Cloud (VPC) |
N/A |
{domainID}.api-vpc.aliyunpds.com |
{regionID}.admin-vpc.aliyunpds.com |
Communication protocols
PDS supports HTTP and HTTPS. We recommend that you use HTTPS to improve communication security.
Request method
Use the POST method for all requests. Include all parameters in the request body.
Request and response format
Requests and responses use the Content-Type: application/json format.
Encoding format
Requests and responses are encoded in UTF-8.