# URL method (pending txs)

**Request Body - `Content-Type: application/json;charset=utf-8`**

| Parameter | Required | Description                                               |
| --------- | -------- | --------------------------------------------------------- |
| `address` | No       | An address value to query pending transaction information |
| `count`   | No       | Number of most recent transactions to return              |

*If the address has fewer transactions than `count`, the returned list of transactions will be of length less than `count`.*GET/api/v3/tx/pending/:address?{count}

**Example request without address**

```
curl -X GET http://localhost:2442/api/v3/tx/pending \
-H 'Content-Type: application/json;charset=utf-8'
```

**Example request without address with count**

```
curl -X GET http://localhost:2442/api/v3/tx/pending\?count\=2 \
-H 'Content-Type: application/json;charset=utf-8'
```

**Example request with address**

```
curl -X GET http://localhost:2442/api/v3/tx/pending/H2hQWtyFT1dvm5o6HvuF1oHq92bbb6ZVY \
-H 'Content-Type: application/json;charset=utf-8'
```

**Example request with address and count**

```
curl -X GET http://localhost:2442/api/v3/tx/pending/H2hQWtyFT1dvm5o6HvuF1oHq92bbb6ZVY\?count\=3 \
-H 'Content-Type: application/json;charset=utf-8'
```


---

# Agent Instructions: 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:

```
GET https://teamhycon.gitbook.io/docs/api-v3-2/untitled-2/url-method-pending-txs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.