# How do I distinguish original X posts, replies and reposts?

How do I distinguish original X posts, replies and reposts? Follow concrete contracts, examples and reviewable steps using X (Twitter).

Canonical page: https://datanavoapi.com/en/answers/x-own-posts-without-retweets/

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

## Answer

Start by inspecting the contracts and local samples for X user posts. Establish the input for x.users.posts.list, then check whether its post object contains the fields your task needs.

Document the input scope, sampling rule and intended use, and preserve request IDs and missing-field markers. An API supplies the contracted sample; interpretation still requires checks of context and representativeness.

## Relevant contracts

| Capability | Object | Shape | Pagination |

| --- | --- | --- | --- |

| x.users.posts.list | Post | items | Explicit cursor |

- [X user posts](https://datanavoapi.com/en/apis/x/users/posts/list/)

## Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

- Only send fields defined for this method; unknown fields are rejected before execution.

| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |

| --- | --- | --- | --- | --- | --- | --- |

| GET | username | string | Required | X handle, without the @ | — | "NASA" |

| GET | tab | string | Optional / conditional | Which tab of the profile: posts (retweets among them), replies (the account's own only: the posts of others it replies to are left out, and parent_id names them), or media | ["posts","replies","media"] | — |

| GET | cursor | string | Optional / conditional | The `next_cursor` of the previous page. A new page is a new call. | — | — |

| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |

| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |

## Complete one verification

Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.

```json
{
  "capability": "x.users.posts.list",
  "method": "GET",
  "params": {
    "username": "NASA"
  }
}
```

## Related pages

- [X user posts](https://datanavoapi.com/en/apis/x/users/posts/list/)
- [X (Twitter) APIs](https://datanavoapi.com/en/apis/x/)
- [X (Twitter) MCP](https://datanavoapi.com/en/mcp/x/)
- [Post fields](https://datanavoapi.com/en/docs/objects/post/)
- [Account review workflow](https://datanavoapi.com/en/skills/account-audit/)
- [How can AI assist an account review?](https://datanavoapi.com/en/answers/ai-account-audit-and-review/)
- [How do I estimate API costs for reviewing X accounts?](https://datanavoapi.com/en/answers/watch-x-accounts-official-api-too-expensive/)

[中文](https://datanavoapi.com/answers/x-own-posts-without-retweets/)
