Endpoints
    GET/desearch/threads/profile/{username}/posts

    Retrieve Threads Profile Posts

    Retrieve a Threads account's latest public posts. Threads shows only the latest 20-30 posts publicly, so there are no further pages. Billed per request, including an empty page. A 404, a 422 and a 5xx are not charged. Billing metadata: successful billable responses include the `X-Desearch-Cost-Usd`, `X-Desearch-Usage-Count`, `X-Desearch-Service`, and `X-Desearch-Currency` headers. JSON object responses also include optional `cost_usd`, `usage_count`, `service`, and `currency` fields. Current prices are at https://desearch.ai/pricing. JSON arrays, text, and streaming responses keep their body shape and expose billing metadata only through headers.

    Base URL

    https://api.desearch.ai

    Implementation guidance

    Use Retrieve Threads Profile Posts when your application needs search-grounded AI results without maintaining its own crawler, social-data pipeline, or retrieval infrastructure. The endpoint returns structured data that can be consumed by agents, research tools, dashboards, and retrieval-augmented generation workflows. Keep the request focused on the minimum fields your workflow needs so responses remain fast and easy to validate.

    Send requests to GET /desearch/threads/profile/{username}/posts with your Desearch API key in the authorization header. Treat the key as a server-side secret, validate all required parameters before sending the request, and handle non-2xx responses explicitly. Production integrations should use sensible timeouts, retry only transient failures with backoff, and record the response status and request identifier for troubleshooting.

    Test the example request below before integrating it into a larger workflow. Confirm that the returned fields, links, and timestamps meet your freshness requirements, then add schema validation at the application boundary. For agentic systems, preserve source URLs with the generated answer so users can inspect evidence and your application can avoid presenting unsupported claims.

    Path Parameters

    usernamestringrequired

    Threads username without @

    Responses

    200A list of normalized Threads posts.
    301Moved Permanently
    304Not Modified
    401Unauthorized
    422Validation Error. Not charged.
    429Too Many Requests
    500Internal Server Error
    Authorization

    Your API key is sent in the Authorization header.

    Request
    curl -X GET "https://api.desearch.ai/desearch/threads/profile/zuck/posts" \
      -H "Authorization: YOUR_API_KEY" \
      -H "Content-Type: application/json"
    ResponseSchema
    [
      {
        "id": "3656367813102434565",
        "code": "DK-BydcJHkF",
        "url": "https://www.threads.com/@zuck/post/DK-BydcJHkF",
        "text": "string",
        "createdAt": "2025-06-16T16:57:11.000Z",
        "author": {
          "id": "63055343223",
          "username": "zuck",
          "fullName": "Mark Zuckerberg",
          "avatar": "string",
          "verified": true
        },
        "likes": 0,
        "replies": 0,
        "reposts": 0,
        "quotes": 0,
        "reshares": 0,
        "views": 0,
        "images": [
          "string"
        ],
        "videos": [
          "string"
        ]
      }
    ]

    Possible status codes:

    200401422429500