> For the complete documentation index, see [llms.txt](https://platformv2docs.chainup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platformv2docs.chainup.com/english-3/contract-transaction.md).

# Contract transaction

## Contract fee inquiry

<mark style="color:green;">`POST`</mark> `https://service.xxx.com/platformapi/chainup/open/futures/feeList`

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

#### Headers

| Name         | Type   | Description      |
| ------------ | ------ | ---------------- |
| Content-Type | String | application/json |

#### Request Body

| Name                                      | Type   | Description                       |
| ----------------------------------------- | ------ | --------------------------------- |
| app\_id<mark style="color:red;">\*</mark> | String | Merchant unique identifier appKey |
| sign<mark style="color:red;">\*</mark>    | String | <p>Signature</p><p><br></p>       |
| data<mark style="color:red;">\*</mark>    | String |                                   |
| time<mark style="color:red;">\*</mark>    | String |                                   |

{% tabs %}
{% tab title="200: OK " %}

```javascript
{
  "code":"",
  "msg":"",
  "sign":"",
  "data":""
}

data:
{
    "count": "20",
    "list": [
        {
            "itemDate": 10008902123, // Date, in timestamp format accurate to seconds
            "uid": "20300021", // User ID
            "coin": "btc", // Coin symbol
            "tradeAmount": "2000", // Trade amount
            "feeAmount": "1" // Fee amount
        }
    ]
}
```

{% endtab %}
{% endtabs %}

The following are the parameters involved in rsa encryption:

<table><thead><tr><th width="136">name</th><th width="124">type</th><th>required</th><th width="214">example</th><th>Description</th></tr></thead><tbody><tr><td>startDate</td><td>String</td><td>YES</td><td>200001</td><td>Start date, accurate to the day, timestamp accurate to the second</td></tr><tr><td>endDate</td><td>String</td><td>YES</td><td>xxxxx@.com</td><td>End date, accurate to the day, timestamp accurate to the second</td></tr><tr><td>page</td><td>String</td><td>NO</td><td>1</td><td>Page number, default 1</td></tr><tr><td>pageSize</td><td>String</td><td>NO</td><td>10</td><td>Items per page, default 100</td></tr></tbody></table>

## Contract broker role inquiry

<mark style="color:green;">`POST`</mark> `https://service.xxx.com/platformapi/chainup/open/futures/agentUser`

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

#### Headers

| Name         | Type   | Description      |
| ------------ | ------ | ---------------- |
| Content-Type | String | application/json |

#### Request Body

| Name                                      | Type   | Description                       |
| ----------------------------------------- | ------ | --------------------------------- |
| app\_id<mark style="color:red;">\*</mark> | String | Merchant unique identifier appKey |
| time<mark style="color:red;">\*</mark>    | String |                                   |
| data<mark style="color:red;">\*</mark>    | String |                                   |
| sign<mark style="color:red;">\*</mark>    | String |                                   |

{% tabs %}
{% tab title="200: OK " %}

```javascript
{
  "code":"",
  "msg":"",
  "data":"",
  "sign":""
}

data:
{
  "count": "sed in ipsum",
  "list": [
    {
      "itemDate": 42617625.97714323,//Date, in timestamp format accurate to seconds
      "uid": "voluptate minim Duis",// User ID
      "coin": "amet sunt est dolore aute",//Coin type
      "tradeAmount": "commodo Excepteur nisi",//Trade amount
      "feeAmount": "amet commodo in Duis nostrud"//手续费
    }
  ]
}
```

{% endtab %}
{% endtabs %}

The following are the parameters involved in rsa encryption:

<table><thead><tr><th width="136">name</th><th width="124">type</th><th>required</th><th width="214">example</th><th>Description</th></tr></thead><tbody><tr><td>startDate</td><td>String</td><td>YES</td><td>200001</td><td>Start date, accurate to the day, timestamp accurate to the second</td></tr><tr><td>endDate</td><td>String</td><td>YES</td><td>xxxxx@.com</td><td>End date, accurate to the day, timestamp accurate to the second</td></tr><tr><td>page</td><td>String</td><td>NO</td><td>1</td><td>Page number, default 1</td></tr><tr><td>pageSize</td><td>String</td><td>NO</td><td>10</td><td>Items per page, default 100</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://platformv2docs.chainup.com/english-3/contract-transaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.