大纸片网络验证

https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095
Admin
大纸片网络验证是一款为个人开发者提供API接口的网络验证服务，旨在帮助开发者轻松地为软件集成卡密功能，实现便捷管理和收费。
Tokens:11,542
Snippets:33
Trust Score:8.7
Update:8 months ago
Show doc for...
Tokens:
Raw
### Custom Variable Interface Request Example (YAML)

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/260841528e0

This YAML snippet demonstrates an example request payload for the Custom Variable Interface. It includes fields such as appid, token, device, varName, timestamp, and sign, which are used for authentication and data transmission.

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /ApiVer/Variable:
    post:
      summary: 自定义变量接口
      deprecated: false
      description: |-
        不开启校验：
        正常请求：APPID+变量名称+时间戳+sign(变量名称+时间戳+APPKEY)
        加密请求：APPID data(变量名称+时间戳+sign)

        开启校验：
        正常请求：APPID+token+变量名称+设备码+时间戳+sign(token+变量名称+设备码+时间戳+APPKEY)
        加密请求：APPID+data(token+变量名称+设备码+时间戳+sign)
      tags:
        - 大纸片API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                appid:
                  type: string
                  description: APPID
                token:
                  type: string
                  description: 卡密token
                device:
                  type: string
                  description: 设备码
                varName:
                  type: string
                  description: 变量名称
                timestamp:
                  type: string
                  description: 时间戳
                sign:
                  type: string
                  description: 签名校验
              required:
                - appid
                - varName
                - timestamp
                - sign
              x-apifox-orders:
                - appid
                - token
                - device
                - varName
                - timestamp
                - sign
            example:
              appid: '1024'
              token: dca36f6e-6811-4f12-ae25-836299899fc0
              device: '123456'
              varName: asdasd
              timestamp: '1739416800'
              sign: 161bda9c85220e2330a16d253adf8f64
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    description: 自定义响应码
                  dzpbt:
                    type: string
                    description: 变量名称&变量内容
                  dzp_time:
                    type: integer
                    description: 时间戳
                  cusVerify:
                    type: string
                    description: 二次校验码
                  sign:
                    type: string
                    description: 签名校验
                required:
                  - code
                  - dzpbt
                  - dzp_time
                  - cusVerify
                  - sign
                x-apifox-orders:
                  - code
                  - dzpbt
                  - dzp_time
                  - cusVerify
                  - sign
              example:
                code: 268
                dzpbt: 这是标题-6661
                dzp_time: 1740201141
                cusVerify: defO7sweY9uPx0vL
                sign: uqZEYmoRdyEyq1zleque
          headers: {}
          x-apifox-name: 成功
      security: []
      x-apifox-folder: 大纸片API
      x-apifox-status: developing
      x-run-in-apifox: https://app.apifox.com/web/project/5543396/apis/api-260841528-run
components:
  schemas: {}
  securitySchemes: {}
servers:
  - url: http://prod-cn.your-api-server.com
    description: 正式环境
security: []

```

--------------------------------

### OpenAPI Specification for Heartbeat Verification Interface

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239567024e0

This OpenAPI 3.0.1 specification defines the Heartbeat Verification Interface. It outlines the request parameters (appid, token, timestamp, sign, and optional encrypted data) and the structure of the JSON response, including success and error examples. The endpoint is designed for POST requests.

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /ApiVer/hbVerifyIntf:
    post:
      summary: 心跳校验接口
      deprecated: false
      description: |-
        心跳校验接口，推荐将全部参数都填写上去，请求参数全部都为json格式

        普通请求：appid+token+timestamp+sign
        加密请求：appid+data(token+timestamp+sign)

        签名校验：token&timestamp&APPKEY(具体请看签名校验文档说明)
      tags:
        - 大纸片API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                appid:
                  type: string
                  description: APP的ID
                token:
                  type: string
                  description: 心跳校验码
                timestamp:
                  type: integer
                  description: 本地时间戳
                sign:
                  type: string
                  description: 签名校验
                data:
                  type: string
                  description: 加密时填写
              required:
                - appid
                - token
              x-apifox-orders:
                - appid
                - token
                - timestamp
                - sign
                - data
            example:
              appid: '1008'
              token: 8d988d5d-a977-4c0f-84f5-05fddfcd7aa1
              timestamp: '1729499434'
              sign: 1303eeecd139f962464e4fd03d6fde1d
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    title: 成功响应码
                  msg:
                    type: string
                    title: 成功提示
                  dzp_time:
                    type: integer
                    title: 服务器时间戳
                  cusVerify:
                    type: string
                    title: 二次校验码
                  sign:
                    type: string
                    title: 签名校验
                required:
                  - code
                  - msg
                  - dzp_time
                  - cusVerify
                  - sign
                x-apifox-orders:
                  - code
                  - msg
                  - dzp_time
                  - cusVerify
                  - sign
              examples:
                '1':
                  summary: 成功示例
                  value:
                    code: 200
                    msg: 心跳包校验成功
                    dzp_time: 1733020660
                    cusVerify: defO7sweY9uPx0vL
                    sign: uqZEYmoRdyEyq1zleque
                '2':
                  summary: 异常示例
                  value:
                    code: '-1000'
                    msg: token不存在
                    dzp_time: 1733211588
                    cusVerify: defO7sweY9uPx0vL
                    sign: 18892974c72493e811273bfe724dbb50
          headers: {}
          x-apifox-name: 成功
      security: []
      x-apifox-folder: 大纸片API
      x-apifox-status: developing
      x-run-in-apifox: https://app.apifox.com/web/project/5543396/apis/api-239567024-run
components:
  schemas: {}
  securitySchemes: {}
servers:
  - url: http://prod-cn.your-api-server.com
    description: 正式环境
security: []

```

--------------------------------

### 卡密激活接口

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/index

Activates a product key (卡密) for the network verification service.

```APIDOC
## POST /api/activate

### Description
This endpoint is used to activate a product key (卡密) for the network verification service. It allows developers to integrate key-based activation into their software.

### Method
POST

### Endpoint
/api/activate

### Parameters
#### Request Body
- **key** (string) - Required - The product key to activate.
- **product_id** (string) - Required - The identifier for the product.

### Request Example
```json
{
  "key": "your_product_key",
  "product_id": "your_product_id"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the activation status (e.g., 'success', 'invalid_key', 'already_activated').
- **message** (string) - A human-readable message explaining the result.

#### Response Example
```json
{
  "status": "success",
  "message": "Key activated successfully."
}
```
```

--------------------------------

### 卡密解绑接口

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/index

Unbinds a product key (卡密) from the current device or session.

```APIDOC
## POST /api/unbind

### Description
This endpoint is used to unbind a previously activated product key (卡密) from the current device or session. This can be useful for allowing users to transfer their license.

### Method
POST

### Endpoint
/api/unbind

### Parameters
#### Request Body
- **key** (string) - Required - The product key to unbind.
- **product_id** (string) - Required - The identifier for the product.

### Request Example
```json
{
  "key": "your_product_key",
  "product_id": "your_product_id"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the unbinding status (e.g., 'success', 'invalid_key', 'not_bound').
- **message** (string) - A human-readable message explaining the result.

#### Response Example
```json
{
  "status": "success",
  "message": "Key unbound successfully."
}
```
```

--------------------------------

### POST /ApiVer/Notice

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239573190e0

This endpoint allows you to query announcements. It's recommended to provide all parameters. Both regular and encrypted requests are supported. For encrypted requests, the response data will be encrypted.

```APIDOC
## POST /ApiVer/Notice

### Description
Queries announcements. It's recommended to provide all parameters. Both regular and encrypted requests are supported. For encrypted requests, the response data will be encrypted.

### Method
POST

### Endpoint
/ApiVer/Notice

### Parameters
#### Query Parameters
None

#### Request Body
- **appid** (string) - Required - APP应用ID
- **timestamp** (integer) - Required - 本地时间戳

### Request Example
```json
{
  "appid": "1008",
  "timestamp": "1729996665"
}
```

### Response
#### Success Response (200)
- **code** (integer) - 成功响应码
- **msg** (string) - 成功提示
- **data** (string) - 公告内容
- **dzp_time** (integer) - 服务器时间戳
- **cusVerify** (string) - 二次校验码
- **sign** (string) - 签名校验

#### Response Example (Success)
```json
{
  "code": 200,
  "msg": "公告获取成功！",
  "data": "这里是公告内容",
  "dzp_time": 1733026708,
  "cusVerify": "defO7sweY9uPx0vL",
  "sign": "uqZEYmoRdyEyq1zleque"
}
```

#### Response Example (Encrypted)
```json
{
  "data": "ttFqv9lk2IZP99BPFNnlw2b/qO144JHE441sExT6/KNdnsNEuuIrHavStz2tG9Pu/1m5zVGC8ll67D05EP8ShJOuvCdR3KuR/+ASE2E6AL+oV9biBwfdBlUowaadiCMMaJvk+qS0IsHDiSkhmvkk0tvHvH2Q2FcCptztT9AD0nArNXNU7+2TTq0Om+tTxSk4mZfwUZmzk7HdN/4CG9H1wNE/mRAOPiZujgSGOImB4EPTAjIhMf5VHzddBhpM9JZ7"
}
```
```

--------------------------------

### 应用更新接口

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/index

Checks for available updates for the application.

```APIDOC
## POST /api/update

### Description
This endpoint allows your application to check if a newer version is available from the 大纸片网络验证 service. It helps in managing application updates seamlessly.

### Method
POST

### Endpoint
/api/update

### Parameters
#### Request Body
- **current_version** (string) - Required - The current version of the application installed.
- **product_id** (string) - Required - The identifier for the product.

### Request Example
```json
{
  "current_version": "1.0.0",
  "product_id": "your_product_id"
}
```

### Response
#### Success Response (200)
- **update_available** (boolean) - True if an update is available, false otherwise.
- **latest_version** (string) - The latest available version (if update_available is true).
- **download_url** (string) - The URL to download the update (if update_available is true).
- **release_notes** (string) - Notes about the latest release (if update_available is true).

#### Response Example
```json
{
  "update_available": true,
  "latest_version": "1.1.0",
  "download_url": "http://example.com/updates/app-v1.1.0.zip",
  "release_notes": "Added new features and bug fixes."
}
```
```

--------------------------------

### POST /ApiVer/CardInterface

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239477523e0

The Card Activation API endpoint is used to verify and activate digital cards. It accepts various parameters including App ID, card key, device code, timestamp, and a signature. Encrypted requests can also be made by sending a 'data' field.

```APIDOC
## POST /ApiVer/CardInterface

### Description
Card verification and activation interface. It is recommended to fill in all parameters. All request parameters are in JSON format.

**Normal Request:** `appid` + `kami` + `device` + `timestamp` + `sign`
**Encrypted Request:** `appid` & `data` (`kami` + `device` + `timestamp` + `sign`)

Signature verification: `kami` & `device` & `timestamp` & `APPKEY` (refer to signature verification documentation for details).

### Method
POST

### Endpoint
/ApiVer/CardInterface

### Parameters
#### Request Body
- **appid** (integer) - Required - The ID of the APP application
- **kami** (string) - Required - The card key
- **device** (string) - Optional - The device code
- **timestamp** (integer) - Optional - Local timestamp
- **sign** (string) - Optional - Signature verification
- **data** (string) - Optional - Use when encrypting

### Request Example
```json
{
  "appid": "1007",
  "kami": "92mDDKba4NB3SY",
  "device": "S3A5D41",
  "timestamp": "1726931720",
  "sign": "01c47fae076dec6bd802c7170beab680"
}
```

### Response
#### Success Response (200)
- **code** (integer) - Response code for success
- **kami** (string) - The activated card key
- **msg** (string) - Return message
- **vip_time** (integer) - Expiration time for single-code cards / remaining times for count-based cards
- **dzp_time** (integer) - Server timestamp
- **cusVerify** (string) - Secondary verification code
- **HbCheck** (string) - Heartbeat verification code
- **sign** (string) - Signature verification

#### Response Example (Success)
```json
{
  "code": 200,
  "kami": "92mDDKba4NB3SY",
  "msg": "[DZP]Card activation successful!",
  "vip_time": 4102243200,
  "dzp_time": 1733019212,
  "cusVerify": "defO7sweY9uPx0vL",
  "HbCheck": "d2b3b44b-f144-4dcc-8dcb-518e958b8299",
  "sign": "uqZEYmoRdyEyq1zleque"
}
```

#### Response Example (Failure)
```json
{
  "code": "-1000",
  "msg": "Card key does not exist",
  "dzp_time": 1733410073,
  "cusVerify": "ZteSYlU52AR8QSZl",
  "sign": "d4b058bf9769234393283b43856efb54"
}
```
```

--------------------------------

### 自定义变量接口

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/index

Retrieves or sets custom variables associated with a verified session or product.

```APIDOC
## POST /api/variables

### Description
This endpoint allows you to manage custom variables associated with your product or a specific verification session. You can use this for storing application-specific data or configurations.

### Method
POST

### Endpoint
/api/variables

### Parameters
#### Request Body
- **action** (string) - Required - The action to perform ('get' or 'set').
- **key** (string) - Optional - The product key (required for 'get' and 'set' if not using session_id).
- **session_id** (string) - Optional - The session ID (required for 'get' and 'set' if not using key).
- **variable_name** (string) - Required - The name of the custom variable.
- **variable_value** (string) - Optional - The value to set for the variable (required for 'set' action).

### Request Example
```json
{
  "action": "get",
  "session_id": "your_session_id",
  "variable_name": "user_level"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the status of the operation (e.g., 'success', 'not_found', 'invalid_action').
- **value** (string) - The value of the variable (for 'get' action).

#### Response Example
```json
{
  "status": "success",
  "value": "admin"
}
```
```

--------------------------------

### POST /ApiVer/NoticeUpdate

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239769512e0

查询应用更新公告接口。此接口用于获取应用的最新更新信息，包括版本号、更新公告内容、更新链接地址以及是否强制更新等。推荐填写所有请求参数，参数格式为JSON。

```APIDOC
## POST /ApiVer/NoticeUpdate

### Description
查询公告接口，推荐将全部参数都填写上去，请求参数全部都为json格式。普通请求、加密请求：appid+timestamp(如果接口加密，请求参数不变，但是返回的数据会加密)。

### Method
POST

### Endpoint
/ApiVer/NoticeUpdate

### Parameters
#### Request Body
- **appid** (string) - Required - APP应用的ID
- **timestamp** (integer) - Required - 时间戳

### Request Example
```json
{
  "appid": "1008",
  "timestamp": "1729996665"
}
```

### Response
#### Success Response (200)
- **code** (integer) - 成功响应码
- **version** (string) - 版本号
- **updateNotice** (string) - 更新公告
- **updateAddress** (string) - 更新链接地址
- **forceUpdate** (string) - 是否强制更新
- **dzp_time** (integer) - 服务器时间戳
- **cusVerify** (string) - 二次校验码
- **sign** (string) - 签名校验

#### Response Example
```json
{
  "code": 0,
  "version": "1.0.0",
  "updateNotice": "修复了一些已知问题，优化了性能。",
  "updateAddress": "https://example.com/update",
  "forceUpdate": "false",
  "dzp_time": 1729996665,
  "cusVerify": "abcdef123456",
  "sign": "a1b2c3d4e5f6"
}
```
```

--------------------------------

### Calculate Request Signature (MD5)

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/5637925m0

This snippet demonstrates how to calculate the 'sign' parameter for API requests. It uses MD5 hashing on a concatenated string of specific parameters (kami, device, timestamp, APPKEY). Device and timestamp are optional but recommended for complete verification.

```pseudocode
MD5(kami&device&timestamp&APPKEY)
```

--------------------------------

### 卡密激活接口 (卡密验证激活) - OpenAPI Specification

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239477523e0

OpenAPI 3.0.1 specification for the Card Activation API. It defines the POST endpoint '/ApiVer/CardInterface' with parameters for appid, kami, device, timestamp, sign, and an optional encrypted 'data' field. The response includes activation status, card key, messages, VIP expiry, server time, and verification codes.

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /ApiVer/CardInterface:
    post:
      summary: 卡密激活接口
      deprecated: false
      description: |-
        卡密验证激活接口，推荐将全部参数都填写上去，请求参数全部都为json格式

        普通请求：appid+kami+device+timestamp+sign
        加密请求：appid&data(kami+device+timestamp+sign)

        请求的签名校验：kami&device&timestamp&APPKEY(具体请看签名校验文档说明)
      tags:
        - 大纸片API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                appid:
                  type: integer
                  description: APP应用的ID
                kami:
                  type: string
                  description: 卡密
                device:
                  type: string
                  description: 设备码
                timestamp:
                  type: integer
                  description: 本地时间戳
                sign:
                  type: string
                  description: 签名校验
                data:
                  type: string
                  description: 加密时填写
              required:
                - appid
                - kami
            example:
              appid: '1007'
              kami: 92mDDKba4NB3SY
              device: S3A5D41
              timestamp: '1726931720'
              sign: 01c47fae076dec6bd802c7170beab680
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    description: 成功响应码
                  kami:
                    type: string
                    description: 激活的卡密
                  msg:
                    type: string
                    description: 返回提示
                  vip_time:
                    type: integer
                    description: 单码卡到期时间/次数卡剩余次数
                  dzp_time:
                    type: integer
                    description: 服务器时间戳
                  cusVerify:
                    type: string
                    description: 二次校验码
                  HbCheck:
                    type: string
                    description: 心跳校验码
                  sign:
                    type: string
                    description: 签名校验
                required:
                  - code
                  - kami
                  - msg
                  - vip_time
                  - dzp_time
                  - cusVerify
                  - HbCheck
                  - sign
              examples:
                '1':
                  summary: 成功示例
                  value:
                    code: 200
                    kami: 92mDDKba4NB3SY
                    msg: '[DZP]卡密激活成功！'
                    vip_time: 4102243200
                    dzp_time: 1733019212
                    cusVerify: defO7sweY9uPx0vL
                    HbCheck: d2b3b44b-f144-4dcc-8dcb-518e958b8299
                    sign: uqZEYmoRdyEyq1zleque
                '2':
                  summary: 失败例子
                  value:
                    code: '-1000'
                    msg: 卡密不存在
                    dzp_time: 1733410073
                    cusVerify: ZteSYlU52AR8QSZl
                    sign: d4b058bf9769234393283b43856efb54
          headers: {}
          x-apifox-name: 成功
      security: []
      x-apifox-folder: 大纸片API
      x-apifox-status: developing
      x-run-in-apifox: https://app.apifox.com/web/project/5543396/apis/api-239477523-run
components:
  schemas: {}
  securitySchemes: {}
servers:
  - url: http://prod-cn.your-api-server.com
    description: 正式环境
security: []

```

--------------------------------

### 公告查询接口

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/index

Retrieves announcements or messages from the verification service.

```APIDOC
## POST /api/announcements

### Description
This endpoint allows you to query for any announcements or important messages published by the 大纸片网络验证 service. This can be used to inform users of updates or maintenance.

### Method
POST

### Endpoint
/api/announcements

### Parameters
#### Query Parameters
- **type** (string) - Optional - Filter announcements by type (e.g., 'system', 'maintenance').

### Request Example
```json
{
  "type": "system"
}
```

### Response
#### Success Response (200)
- **announcements** (array) - A list of announcement objects.
  - **title** (string) - The title of the announcement.
  - **content** (string) - The main content of the announcement.
  - **timestamp** (string) - The time the announcement was published.

#### Response Example
```json
{
  "announcements": [
    {
      "title": "System Update",
      "content": "Scheduled maintenance will occur on Sunday.",
      "timestamp": "2023-10-27T10:00:00Z"
    }
  ]
}
```
```

--------------------------------

### 心跳校验接口

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/index

Performs a heartbeat check to maintain the active status of a verified session.

```APIDOC
## POST /api/heartbeat

### Description
This endpoint is used to send a heartbeat signal to the verification server, indicating that the client application is still active and verified. This is crucial for maintaining continuous verification status.

### Method
POST

### Endpoint
/api/heartbeat

### Parameters
#### Request Body
- **session_id** (string) - Required - The unique identifier for the current verification session.

### Request Example
```json
{
  "session_id": "your_session_id"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the heartbeat status (e.g., 'ok', 'session_expired', 'invalid_session').
- **message** (string) - A human-readable message explaining the result.

#### Response Example
```json
{
  "status": "ok",
  "message": "Heartbeat received."
}
```
```

--------------------------------

### POST /ApiVer/hbVerifyIntf

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239567024e0

Performs a heartbeat verification. It is recommended to provide all parameters. Requests can be in plain JSON format or encrypted.

```APIDOC
## POST /ApiVer/hbVerifyIntf

### Description
Performs a heartbeat verification. It is recommended to provide all parameters. Requests can be in plain JSON format or encrypted. Plain requests include `appid`, `token`, `timestamp`, and `sign`. Encrypted requests include `appid` and `data` (which contains `token`, `timestamp`, and `sign`). Signature validation is required.

### Method
POST

### Endpoint
/ApiVer/hbVerifyIntf

### Parameters
#### Request Body
- **appid** (string) - Required - The ID of the APP.
- **token** (string) - Required - The heartbeat verification code.
- **timestamp** (integer) - Optional - The local timestamp.
- **sign** (string) - Optional - The signature for verification.
- **data** (string) - Optional - Used for encrypted requests.

### Request Example
```json
{
  "appid": "1008",
  "token": "8d988d5d-a977-4c0f-84f5-05fddfcd7aa1",
  "timestamp": "1729499434",
  "sign": "1303eeecd139f962464e4fd03d6fde1d"
}
```

### Response
#### Success Response (200)
- **code** (integer) - The response code indicating success.
- **msg** (string) - A message indicating the result of the verification.
- **dzp_time** (integer) - The server timestamp.
- **cusVerify** (string) - A secondary verification code.
- **sign** (string) - The signature for verification.

#### Response Example
```json
{
  "code": 200,
  "msg": "心跳包校验成功",
  "dzp_time": 1733020660,
  "cusVerify": "defO7sweY9uPx0vL",
  "sign": "uqZEYmoRdyEyq1zleque"
}
```

#### Error Response Example
```json
{
  "code": "-1000",
  "msg": "token不存在",
  "dzp_time": 1733211588,
  "cusVerify": "defO7sweY9uPx0vL",
  "sign": "18892974c72493e811273bfe724dbb50"
}
```
```

--------------------------------

### Calculate Response Signature (MD5)

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/5637925m0

This snippet illustrates the calculation of the 'sign' parameter for API responses. It involves concatenating all response parameters except 'sign' itself, then applying MD5 hashing along with the APPKEY. The resulting signature is compared with the 'sign' provided in the response.

```pseudocode
MD5(code&msg&dzp_time&cusVerify&APPKEY)
```

--------------------------------

### Application Update Interface Specification (YAML)

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239769512e0

This YAML snippet defines the OpenAPI 3.0.1 specification for the application update interface. It includes the endpoint `/ApiVer/NoticeUpdate`, its summary, description, request body schema (appid, timestamp), and response schema (code, version, updateNotice, updateAddress, forceUpdate, dzp_time, cusVerify, sign).

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /ApiVer/NoticeUpdate:
    post:
      summary: 应用更新接口
      deprecated: false
      description: |-
        查询公告接口，推荐将全部参数都填写上去，请求参数全部都为json格式

        普通请求、加密请求：appid+timestamp(如果接口加密，请求参数不变，但是返回的数据会加密)
      tags:
        - 大纸片API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                appid:
                  type: string
                  description: APP应用的ID
                timestamp:
                  type: integer
                  description: 时间戳
              required:
                - appid
              x-apifox-orders:
                - appid
                - timestamp
            example:
              appid: '1008'
              timestamp: '1729996665'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    description: 成功响应码
                  version:
                    type: string
                    description: 版本号
                  updateNotice:
                    type: string
                    description: 更新公告
                  updateAddress:
                    type: string
                    description: 更新链接地址
                  forceUpdate:
                    type: string
                    description: 是否强制更新
                  dzp_time:
                    type: integer
                    description: 服务器时间戳
                  cusVerify:
                    type: string
                    description: 二次校验码
                  sign:
                    type: string
                    description: 签名校验
                required:
                  - code
                  - version
                  - updateNotice
                  - updateAddress
                  - forceUpdate
                  - dzp_time
                  - cusVerify
                  - sign
                x-apifox-orders:
                  - code
                  - version
                  - updateNotice
                  - updateAddress
                  - forceUpdate
                  - dzp_time
                  - cusVerify
                  - sign
          headers: {}
          x-apifox-name: 成功
      security: []
      x-apifox-folder: 大纸片API
      x-apifox-status: developing
      x-run-in-apifox: https://app.apifox.com/web/project/5543396/apis/api-239769512-run
components:
  schemas: {}
  securitySchemes: {}
servers:
  - url: http://prod-cn.your-api-server.com
    description: 正式环境
security: []

```

--------------------------------

### POST /ApiVer/CardUnbind

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239720265e0

The Card Unbind API is used to unbind card credentials. It is recommended to provide all parameters. Requests can be made in plain text or encrypted format.

```APIDOC
## POST /ApiVer/CardUnbind

### Description
Unbinds card credentials. Supports plain text requests (appid+kami+device+timestamp+sign) and encrypted requests (appid&data(kami+device+timestamp+sign)). Signature verification is required.

### Method
POST

### Endpoint
/ApiVer/CardUnbind

### Parameters
#### Query Parameters
None

#### Request Body
- **appid** (string) - Required - APP application ID
- **kami** (string) - Required - Card credential
- **device** (string) - Optional - Device code
- **timestamp** (integer) - Optional - Timestamp
- **sign** (string) - Optional - Signature verification
- **data** (string) - Optional - Encrypted data (used for encrypted requests)

### Request Example
```json
{
  "appid": "1008",
  "kami": "92mDDKba4NB3SY",
  "device": "S3A541",
  "timestamp": "1726931720",
  "sign": "333bde277fb9ce04df696a013b9e565a"
}
```

### Response
#### Success Response (200)
- **code** (integer) - Response code
- **msg** (string) - Response message
- **dzp_time** (integer) - Server timestamp
- **cusVerify** (string) - Secondary verification code
- **sign** (string) - Signature verification

#### Response Example (Success)
```json
{
  "code": 200,
  "msg": "卡密解绑成功",
  "dzp_time": 1733112162,
  "cusVerify": "defO7sweY9uPx0vL",
  "sign": "uqZEYmoRdyEyq1zleque"
}
```

#### Response Example (Error)
```json
{
  "code": -1009,
  "msg": "卡密解绑次数不足",
  "dzp_time": 1733112248,
  "cusVerify": "defO7sweY9uPx0vL",
  "sign": "db3d0d09dfe15053c914eb111b9c878c"
}
```
```

--------------------------------

### 公告查询接口 OpenAPI Specification (YAML)

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/239573190e0

The OpenAPI 3.0.1 specification for the '公告查询接口' POST endpoint. It defines request parameters (appid, timestamp) and response fields (code, msg, data, dzp_time, cusVerify, sign). Supports both plain and encrypted data.

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /ApiVer/Notice:
    post:
      summary: 公告查询接口
      deprecated: false
      description: |-
        查询公告接口，推荐将全部参数都填写上去，请求参数全部都为json格式

        普通请求、加密请求：appid+timestamp(如果接口加密，请求参数不变，但是返回的数据会加密)
      tags:
        - 大纸片API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                appid:
                  type: string
                  description: APP应用的ID
                timestamp:
                  type: integer
                  description: 本地时间戳
              required:
                - appid
              x-apifox-orders:
                - appid
                - timestamp
            example:
              appid: '1008'
              timestamp: '1729996665'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    description: 成功响应码
                  msg:
                    type: string
                    description: 成功提示
                  data:
                    type: string
                    description: 公告内容
                  dzp_time:
                    type: integer
                    description: 服务器时间戳
                  cusVerify:
                    type: string
                    description: 二次校验码
                  sign:
                    type: string
                    description: 签名校验
                required:
                  - code
                  - msg
                  - data
                  - dzp_time
                  - cusVerify
                  - sign
                x-apifox-orders:
                  - code
                  - msg
                  - data
                  - dzp_time
                  - cusVerify
                  - sign
              examples:
                '1':
                  summary: 成功示例
                  value:
                    code: 200
                    msg: 公告获取成功！
                    data: |
                      这里是公告内容
                    dzp_time: 1733026708
                    cusVerify: defO7sweY9uPx0vL
                    sign: uqZEYmoRdyEyq1zleque
                '2':
                  summary: 加密示例
                  value:
                    data: >-
                      ttFqv9lk2IZP99BPFNnlw2b/qO144JHE441sExT6/KNdnsNEuuIrHavStz2tG9Pu/1m5zVGC8ll67D05EP8ShJOuvCdR3KuR/+ASE2E6AL+oV9biBwfdBlUowaadiCMMaJvk+qS0IsHDiSkhmvkk0tvHvH2Q2FcCptztT9AD0nArNXNU7+2TTq0Om+tTxSk4mZfwUZmzk7HdN/4CG9H1wNE/mRAOPiZujgSGOImB4EPTAjIhMf5VHzddBhpM9JZ7
          headers: {}
          x-apifox-name: 成功
      security: []
      x-apifox-folder: 大纸片API
      x-apifox-status: developing
      x-run-in-apifox: https://app.apifox.com/web/project/5543396/apis/api-239573190-run
components:
  schemas: {}
  securitySchemes: {}
servers:
  - url: http://prod-cn.your-api-server.com
    description: 正式环境
security: []

```

--------------------------------

### POST /ApiVer/Variable

Source: https://s.apifox.cn/a9211e64-fde9-422b-adcc-aa9fbb9a4095/260841528e0

This endpoint allows for the management of custom variables. It supports different request formats including normal and encrypted requests, with optional validation enabled by a token and device code.

```APIDOC
## POST /ApiVer/Variable

### Description
This endpoint manages custom variables. It supports two modes: without validation and with validation. The request format varies based on the mode, involving parameters like APPID, variable name, timestamp, sign, token, and device code. Encrypted requests use a 'data' field.

### Method
POST

### Endpoint
/ApiVer/Variable

### Parameters
#### Query Parameters
(No query parameters defined in the OpenAPI spec)

#### Request Body
- **appid** (string) - Required - APPID
- **token** (string) - Optional - Card password token
- **device** (string) - Optional - Device code
- **varName** (string) - Required - Variable name
- **timestamp** (string) - Required - Timestamp
- **sign** (string) - Required - Signature verification

### Request Example
```json
{
  "appid": "1024",
  "token": "dca36f6e-6811-4f12-ae25-836299899fc0",
  "device": "123456",
  "varName": "asdasd",
  "timestamp": "1739416800",
  "sign": "161bda9c85220e2330a16d253adf8f64"
}
```

### Response
#### Success Response (200)
- **code** (integer) - Custom response code
- **dzpbt** (string) - Variable name & variable content
- **dzp_time** (integer) - Timestamp
- **cusVerify** (string) - Secondary verification code
- **sign** (string) - Signature verification

#### Response Example
```json
{
  "code": 268,
  "dzpbt": "这是标题-6661",
  "dzp_time": 1740201141,
  "cusVerify": "defO7sweY9uPx0vL",
  "sign": "uqZEYmoRdyEyq1zleque"
}
```
```
Tokens:
Raw