Demo
Updated: 2023-11-14 14:07:19
API Description
1、
2、接口支持https协议
API URL
Request Method
API Constraints
The API supports both HTTP and HTTPS. HTTPS is recommended to ensure security. API calls are subject to rate limits. See details
Request Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| appId | true | String | Account appId [See Get Secret Key] |
| timestamp | true | Long | Current 13-digit millisecond timestamp, valid within 3 minutes |
| sign | true | String | Signature, a 32-character uppercase MD5 value. The appSecret used to generate the signature is critical for communication data security. It must never be used directly on the client side. All APIs must be called through your own server to relay requests to the POLYV server for response data. [See Signature Generation Rules] |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | Integer | Response status code, 200 for success, non-200 for failure [See Global Error Description] |
| status | String | Response status text |
| message | String | Response description, provides error details when code is 400 or 500 |
| data |
Java Request Example
For quick integration, download the relevant dependency source code. Click here to download the source code. After downloading, add it to your project source code. The test cases include HttpUtil.java and LiveSignUtil.java, both contained in the download file.
It is strongly recommended to use the Live Java SDK for API integration. The Live Java SDK provides unified encapsulation and optimization for API call logic, exception handling, data signing, and HTTP request thread pools.
Response Example
For global system error descriptions, see Global Error Description
Success Example
Error Example
{
"code": 400,
"status": "error",
"message": "invalid signature.",
"data": ""
}
