---
title: "List an X account's posts"
description: "Run job:x.user.posts through the looot API: 3 providers, from $0.00018 per result. Inputs, prices, output shape and code for curl, JavaScript and Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

List an X account's posts.

Job id `x.user.posts`, in [Social data](/catalog/social) (X). As of 2026-10-01, 3 providers serve it through 4 tools. Run `job:x.user.posts` and looot picks one of them; with `fallback` on, a miss moves on to the next. See [Jobs](/concepts/jobs).

## Inputs

A job run takes shared input names; looot maps them to each provider's own fields. See [Job inputs](/concepts/job-inputs).

| Input | Taken by |
| --- | --- |
| `handle` | 2 of 2 providers |
| `limit` | 1 of 2 providers |

Any other key you send passes through unchanged. Each tool's own fields are on its page below.

## Providers and prices

| Provider | Tool | Price |
| --- | --- | --- |
| [Anysite](/providers/anysite) | [`anysite-api-twitter-user-posts`](/reference/tools/anysite-api-twitter-user-posts) | $0.00018 per result |
| AnyAPI | [`anyapi-run-twitter-user-tweets`](/reference/tools/anyapi-run-twitter-user-tweets) | $0.0005 per call |
| AnyAPI | [`anyapi-run-twitter-user-posts`](/reference/tools/anyapi-run-twitter-user-posts) | $0.00075 per call |
| [ScrapeCreators](/providers/scrapecreators) | [`scrapecreators-twitter-user-tweets`](/reference/tools/scrapecreators-twitter-user-tweets) | $0.00188 per call |

A call that fails at the provider costs $0. See [What's free](/money/free-and-failures).

## Output

Each provider answers in its own shape. Shape of the run's `result` from [`scrapecreators-twitter-user-tweets`](/reference/tools/scrapecreators-twitter-user-tweets), the expected shape, not yet checked against real answers:

```txt
{ tweets: { url, core: {}, views: { count, state }, legacy: { lang, id_str, favorited, full_text, bookmarked, created_at, quote_count, bookmark_count, favorite_count, is_quote_status, conversation_id_str, quoted_status_id_str }, source, rest_id, __typename, note_tweet: { is_expandable }, edit_control: { edits_remaining, is_edit_eligible, editable_until_msecs }, unmention_data: {}, is_translatable, quoted_status_result: {}, quick_promote_eligibility: { eligibility } }[], success, credits_charged, credits_remaining }
```

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With `wait: 30` the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll `GET /v1/runs/<runId>`.

Example input with placeholder values:

<CodeGroup>

```bash curl
curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:x.user.posts","input":{"user":"<user>","count":1},"wait":30}'
```

```js JavaScript
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:x.user.posts",
    input: {
      user: "<user>",
      count: 1,
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:x.user.posts",
        "input": {
            "user": "<user>",
            "count": 1,
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To pin one provider, send its tool id as `endpointId` instead of `job:x.user.posts`.