# Threads user replies

Get Threads user's reply list. Needs user id. Served by TikHub.

Purpose:
- Get Threads user's reply list

⚠️ No pagination
- A single call returns all available data (~25 items). There is no way to fetch more.
- The `end_cursor` parameter is reserved and currently has no effect — do not rely on it.

Parameters:
- user_id: User ID, for example: 63625256886
- end_cursor: Pagination cursor. No pagination supported; passing it has no effect
Return:
- User reply list data, including:
    - threads: Reply list
    - next_cursor: Next page cursor (always null)
    - has_more: Has more data

- Tool ID: `tikhub/threads-web-fetch-user-replies`
- Name in the catalog: Threads, Get user replies (no pagination)
- Provider: [TikHub](/providers/tikhub.md)
- Capability: [Threads profiles](/tools/threads/profiles.md)
- Price: $0.002 per call
- Authentication: an authorised Agentik workspace is required for execution, including zero-price tools.

## Pricing contract

The provider’s price, with no markup. Billed for measured usage.


```json
{
  "model": "per_call",
  "amountUsd": 0.002
}
```

Pricing source: [https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info](https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info). Official per-success route price USD 0.002; daily upstream discounts may reduce provider cost. No discount invented for the customer. 3/second.

Price verification date: 2026-10-05.

## Complete input schema


```json
{
  "type": "object",
  "properties": {
    "user_id": {
      "type": "string",
      "description": "用户ID/User ID",
      "title": "User Id"
    },
    "end_cursor": {
      "type": "string",
      "description": "分页游标（本接口不支持分页，传入无效）/Pagination cursor (no pagination, has no effect)",
      "title": "End Cursor"
    }
  },
  "required": [
    "user_id"
  ],
  "additionalProperties": false
}
```

## Published example

This is the provider tool’s published example. Replace example values with the user’s requested inputs, respecting the schema; do not execute an example merely to test a connection.


```json
{
  "tool_id": "tikhub/threads-web-fetch-user-replies",
  "input": {
    "user_id": "63625256886"
  }
}
```

## Execute and retrieve

Inspect again before execution, explain the price and obtain the required authority. Use MCP run_tool or POST /v1/run with this tool ID, valid input and an idempotency key. Save the returned run ID and follow the actual state. If Agentik answers that the tool is temporarily unavailable, do not retry it blindly; use discovery to propose an alternative.

A partial or uncertain result can still have consumed provider resources. Consult [billing](/docs/billing.md), [idempotency](/docs/idempotency.md) and [asynchronous results](/docs/async.md).

[Provider documentation](https://api.tikhub.io/#/Threads-Web-API/fetch_user_replies_api_v1_threads_web_fetch_user_replies_get)

[REST inspection](https://api.agentik.cc/v1/tools/tikhub/threads-web-fetch-user-replies) · [OpenAPI](/openapi.json) · [Connection guide](/connect.md)

---

[HTML page](/providers/tikhub/threads-web-fetch-user-replies) · [Agent index](/llms.txt)