Docs menu

X API endpoint

List public X profile posts API

Use Crawlora's List public X profile posts API to extract supported public X data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.

GETapiKey8 credits/requestXx.profilePostsResponseDoc/x/profile/{username}/posts

Endpoint facts

Method: GET
API path: /x/profile/{username}/posts
Auth: apiKey
Credits: 8 credits/request
Platform: X
Response schema: #/definitions/x.profilePostsResponseDoc
MCP tool: x_profile_posts

Overview

Returns posts present in the first public profile page payload for an X username. The endpoint does not paginate replies, media-only tabs, or search results. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

X scraping API Try List public X profile posts API in Playground Crawlora API pricing X API documentation

Request parameters

Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.

Parameter	Type	Required	Default	Description
username (path)	string	Yes		X username
limit	integer	No	20 and must be 1-50	Maximum posts returned from the first page payload. Defaults to 20 and must be 1-50.
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/x/profile/%3Cusername%3E/posts?limit=10" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost: 8 credits/request
Charged response: Successful 2xx responses

Plan	Price	Included credits	Daily cap	Rate limit	Overage
Free	$0/mo	2,000	500 daily credits	5/min	No overage
Starter	$9/mo	20,000	5,000 daily credits	15/min	$0.75/1,000 overage credits when enabled
Growth	$29/mo	100,000	25,000 daily credits	45/min	$0.45/1,000 overage credits when enabled
Pro	$79/mo	400,000	No daily cap	120/min	$0.30/1,000 overage credits
Business	$199/mo	1,200,000	No daily cap	300/min	$0.20/1,000 overage credits
Enterprise	$499/mo	5,000,000	No daily cap	1,000/min	$0.12/1,000 overage credits

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

Proxy strategy: managed automatically where needed
Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
Browser cluster: supported dynamic workloads can be routed through distributed browser instances
Retry behavior: automatic retry/fallback may be used depending on endpoint type
Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
Billing: credits are charged only for successful 2xx responses
Observability: responses include request context where available

MCP

MCP URL: https://mcp.crawlora.net/mcp
Tool name: x_profile_posts
Transport: Streamable HTTP
Auth: Authorization: Bearer $CRAWLORA_API_KEY
Docs resource: docs://index

Response behavior

- Returns only posts available in the initial public profile page payload. - Returns 404 when the profile is not public or the returned profile does not match the requested username. - Returns 503 when X does not provide the public page payload or the payload shape is not parseable. Example response: ```json { "code": 200, "msg": "OK", "data": { "username": "Ansel_Flipradio", "url": "https://x.com/Ansel_Flipradio", "count": 1, "posts": [ { "id": "1860888559739343022", "url": "https://x.com/Ansel_Flipradio/status/1860888559739343022", "text": "Example public profile post text", "author": { "id": "1634026666518519808", "username": "Ansel_Flipradio", "name": "Fear_Nation_世界苦茶", "url": "https://x.com/Ansel_Flipradio" } } ] } } ```

Catalog quality warnings

missing example for required path param: username

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

Status	Common failure case
400	Invalid input or missing required parameter
429	Plan or endpoint rate limit exceeded
500	Internal execution error
502	Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Failure responses

Status	Description	Schema
400	Missing or invalid parameters	#/definitions/app.Response
404	Profile not found	#/definitions/app.Response
503	Upstream error or parser drift	#/definitions/app.Response

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "username": "Ansel_Flipradio",
    "url": "https://x.com/Ansel_Flipradio",
    "count": 1,
    "posts": [
      {
        "id": "1860888559739343022",
        "url": "https://x.com/Ansel_Flipradio/status/1860888559739343022",
        "text": "Example public profile post text",
        "author": {
          "id": "1634026666518519808",
          "username": "Ansel_Flipradio",
          "name": "Fear_Nation_世界苦茶",
          "url": "https://x.com/Ansel_Flipradio"
        }
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/x.profilePostsResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	x.ProfilePosts	No
data.count	integer	No
data.posts	array	No
data.posts[].author	x.User	No
data.posts[].author.avatar_url	string	No
data.posts[].author.banner_url	string	No
data.posts[].author.id	string	No
data.posts[].author.is_blue_verified	boolean	No
data.posts[].author.is_protected	boolean	No
data.posts[].author.name	string	No
data.posts[].author.url	string	No
data.posts[].author.username	string	No
data.posts[].created_at	string	No
data.posts[].id	string	No
data.posts[].metrics	x.Metrics	No
data.posts[].metrics.bookmarks	integer	No
data.posts[].metrics.likes	integer	No
data.posts[].metrics.replies	integer	No
data.posts[].metrics.reposts	integer	No
data.posts[].metrics.views	integer	No
data.posts[].quoted	x.PostQuote	No
data.posts[].quoted.author	x.User	No
data.posts[].quoted.author.avatar_url	string	No
data.posts[].quoted.author.banner_url	string	No
data.posts[].quoted.author.id	string	No
data.posts[].quoted.author.is_blue_verified	boolean	No
data.posts[].quoted.author.is_protected	boolean	No
data.posts[].quoted.author.name	string	No
data.posts[].quoted.author.url	string	No
data.posts[].quoted.author.username	string	No
data.posts[].quoted.created_at	string	No
data.posts[].quoted.id	string	No
data.posts[].quoted.text	string	No
data.posts[].quoted.url	string	No
data.posts[].text	string	No
data.posts[].url	string	No
data.url	string	No
data.username	string	No
msg	string	No	OK

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/x/profile/%3Cusername%3E/posts?limit=10" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

More X endpoint docs X scraping API Crawlora API pricing Try List public X profile posts API in Playground Retrieve an X post API documentation Retrieve an X profile API documentation

Open in Playground Back to group

Docs menu

X API endpoint

List public X profile posts API

GETapiKey8 credits/requestXx.profilePostsResponseDoc/x/profile/{username}/posts

Endpoint facts

Method: GET
API path: /x/profile/{username}/posts
Auth: apiKey
Credits: 8 credits/request
Platform: X
Response schema: #/definitions/x.profilePostsResponseDoc
MCP tool: x_profile_posts

Overview

X scraping API Try List public X profile posts API in Playground Crawlora API pricing X API documentation

Request parameters

Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.

Parameter	Type	Required	Default	Description
username (path)	string	Yes		X username
limit	integer	No	20 and must be 1-50	Maximum posts returned from the first page payload. Defaults to 20 and must be 1-50.
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/x/profile/%3Cusername%3E/posts?limit=10" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost: 8 credits/request
Charged response: Successful 2xx responses

Plan	Price	Included credits	Daily cap	Rate limit	Overage
Free	$0/mo	2,000	500 daily credits	5/min	No overage
Starter	$9/mo	20,000	5,000 daily credits	15/min	$0.75/1,000 overage credits when enabled
Growth	$29/mo	100,000	25,000 daily credits	45/min	$0.45/1,000 overage credits when enabled
Pro	$79/mo	400,000	No daily cap	120/min	$0.30/1,000 overage credits
Business	$199/mo	1,200,000	No daily cap	300/min	$0.20/1,000 overage credits
Enterprise	$499/mo	5,000,000	No daily cap	1,000/min	$0.12/1,000 overage credits

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

Proxy strategy: managed automatically where needed
Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
Browser cluster: supported dynamic workloads can be routed through distributed browser instances
Retry behavior: automatic retry/fallback may be used depending on endpoint type
Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
Billing: credits are charged only for successful 2xx responses
Observability: responses include request context where available

MCP

MCP URL: https://mcp.crawlora.net/mcp
Tool name: x_profile_posts
Transport: Streamable HTTP
Auth: Authorization: Bearer $CRAWLORA_API_KEY
Docs resource: docs://index

Response behavior

Catalog quality warnings

missing example for required path param: username

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

Status	Common failure case
400	Invalid input or missing required parameter
429	Plan or endpoint rate limit exceeded
500	Internal execution error
502	Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Failure responses

Status	Description	Schema
400	Missing or invalid parameters	#/definitions/app.Response
404	Profile not found	#/definitions/app.Response
503	Upstream error or parser drift	#/definitions/app.Response

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "username": "Ansel_Flipradio",
    "url": "https://x.com/Ansel_Flipradio",
    "count": 1,
    "posts": [
      {
        "id": "1860888559739343022",
        "url": "https://x.com/Ansel_Flipradio/status/1860888559739343022",
        "text": "Example public profile post text",
        "author": {
          "id": "1634026666518519808",
          "username": "Ansel_Flipradio",
          "name": "Fear_Nation_世界苦茶",
          "url": "https://x.com/Ansel_Flipradio"
        }
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/x.profilePostsResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	x.ProfilePosts	No
data.count	integer	No
data.posts	array	No
data.posts[].author	x.User	No
data.posts[].author.avatar_url	string	No
data.posts[].author.banner_url	string	No
data.posts[].author.id	string	No
data.posts[].author.is_blue_verified	boolean	No
data.posts[].author.is_protected	boolean	No
data.posts[].author.name	string	No
data.posts[].author.url	string	No
data.posts[].author.username	string	No
data.posts[].created_at	string	No
data.posts[].id	string	No
data.posts[].metrics	x.Metrics	No
data.posts[].metrics.bookmarks	integer	No
data.posts[].metrics.likes	integer	No
data.posts[].metrics.replies	integer	No
data.posts[].metrics.reposts	integer	No
data.posts[].metrics.views	integer	No
data.posts[].quoted	x.PostQuote	No
data.posts[].quoted.author	x.User	No
data.posts[].quoted.author.avatar_url	string	No
data.posts[].quoted.author.banner_url	string	No
data.posts[].quoted.author.id	string	No
data.posts[].quoted.author.is_blue_verified	boolean	No
data.posts[].quoted.author.is_protected	boolean	No
data.posts[].quoted.author.name	string	No
data.posts[].quoted.author.url	string	No
data.posts[].quoted.author.username	string	No
data.posts[].quoted.created_at	string	No
data.posts[].quoted.id	string	No
data.posts[].quoted.text	string	No
data.posts[].quoted.url	string	No
data.posts[].text	string	No
data.posts[].url	string	No
data.url	string	No
data.username	string	No
msg	string	No	OK

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/x/profile/%3Cusername%3E/posts?limit=10" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Read Crawlora terms

More X endpoint docs X scraping API Crawlora API pricing Try List public X profile posts API in Playground Retrieve an X post API documentation Retrieve an X profile API documentation

Open in Playground Back to group

List public X profile posts API

Endpoint facts

Overview

Request parameters

cURL example

Authentication

Billing

Infrastructure behavior

MCP

Response behavior

Catalog quality warnings

Error behavior

Failure responses

Example JSON response

Code examples

Responsible public web data workflows

Related

List public X profile posts API

Endpoint facts

Overview

Request parameters

cURL example

Authentication

Billing

Infrastructure behavior

MCP

Response behavior

Catalog quality warnings

Error behavior

Failure responses

Example JSON response

Code examples

Responsible public web data workflows

Related