> ## Documentation Index > Fetch the complete documentation index at: https://docs.scraperize.com/llms.txt > Use this file to discover all available pages before exploring further. # Get a community's tweets > Fetches the tweet timeline of a public X Community (`x.com/i/communities/`, logged-out). Each tweet is fully shaped WITH its author (community tweets come from many members). Returns the batch present on the initial page load. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/twitter/community/tweets openapi: 3.0.3 info: title: Scraperize API version: 1.0.0 description: >- Extract public data from social media platforms as clean JSON. Endpoints are split by platform and by what they return, e.g. `GET /v1/twitter/tweet`. ## Authentication Send your API key in the `x-api-key` header (or `Authorization: Bearer `). Create keys in your dashboard. ## Credits Each successful live scrape costs **1 credit**. Credits are prepaid and never expire. ## Caching Every endpoint accepts an optional `cache_max_age` (`1d`|`3d`|`7d`|`14d`|`30d`). A cache hit within that window is returned for **0 credits**. ## Responses Success returns `{ "data": …, "meta": { "requestId", … } }`. Errors return `{ "error": { "code", "message", "requestId" } }` with a matching HTTP status. `meta` on a scrape carries `creditsCharged`, `creditsRemaining`, `cached`, and (on a hit) `cachedAt`. ## Rate limits Requests are limited per team per minute; over the limit returns `429` with a `Retry-After` header. servers: - url: https://api.scraperize.com description: Production security: - ApiKeyAuth: [] tags: - name: Twitter description: Twitter / X scraping endpoints - name: Facebook description: Facebook scraping endpoints - name: Linkme description: Linkme (link.me) scraping endpoints - name: Amazon description: Amazon (creator shop / storefront) scraping endpoints - name: Linkbio description: Linkbio (lnk.bio) scraping endpoints - name: Pillar description: Pillar (pillar.io) scraping endpoints - name: Komi description: Komi (komi.io) scraping endpoints - name: Linktree description: Linktree (linktr.ee) scraping endpoints - name: Kick description: Kick (kick.com) scraping endpoints - name: Snapchat description: Snapchat (snapchat.com) scraping endpoints - name: Telegram description: Telegram (t.me) scraping endpoints - name: Google description: Google Search scraping endpoints paths: /v1/twitter/community/tweets: get: tags: - Twitter summary: Get a community's tweets description: >- Fetches the tweet timeline of a public X Community (`x.com/i/communities/`, logged-out). Each tweet is fully shaped WITH its author (community tweets come from many members). Returns the batch present on the initial page load. parameters: - name: url in: query required: true description: Community URL, e.g. https://x.com/i/communities/1433869915434278912 schema: type: string example: https://x.com/i/communities/1433869915434278912 - name: cache_max_age in: query required: false description: >- Optional. Return a cached result if one this age or newer exists — served for **0 credits** with `meta.cached=true` and `meta.cachedAt`. Otherwise a fresh scrape runs (**1 credit**) and refreshes the cache. Omit to always scrape fresh. schema: type: string enum: - 1d - 3d - 7d - 14d - 30d example: 7d responses: '200': description: The community's tweets. content: application/json: schema: type: object properties: data: type: object properties: communityId: type: string nullable: true tweets: type: array items: type: object tweetCount: type: integer fetchedAt: type: string format: date-time meta: type: object description: >- requestId + credit/caching metadata (creditsCharged, creditsRemaining, cached, cachedAt). required: - data - meta example: data: communityId: '1433869915434278912' tweets: - id: '2090485026769051927' url: https://x.com/d2fl/status/2090485026769051927 text: >- Communities are not gone. I still run several as admin/mod and just joined another active one this week. Some things stay broken: a lot of posts still miss the community tag line, and there is still no way to turn off “share to followers” in many rooms. But the core still works. People can find real groups of like-minded users, pin posts, and moderate. If you locate an active community that people actually visit, joining and posting has almost no downside. A few follows can still trickle in from the right rooms. isLongForm: true lang: null createdAtMs: 1787245444000 createdAt: '2026-08-20T17:04:04.000Z' counts: likes: 34 retweets: 4 replies: 5 quotes: null bookmarks: 4 views: '19759' author: id: '43095363' name: Tom Finnell screenName: d2fl url: https://x.com/d2fl bio: null avatarUrl: >- https://pbs.twimg.com/profile_images/2077515363525271552/APh2RAru_normal.jpg avatarUrlHd: >- https://pbs.twimg.com/profile_images/2077515363525271552/APh2RAru_400x400.jpg followers: 11499 following: 7542 tweetCount: 136377 verified: true verifiedType: null protected: false profileImageShape: Circle professionalCategory: null media: - type: photo id: '2090484840042741760' thumbnailUrl: https://pbs.twimg.com/media/HQLk4tsWQAALWid.jpg altText: null width: 1408 height: 1408 durationMillis: null bestVideoUrl: null variants: [] sourceStatusId: null sensitiveMediaWarning: null additionalMediaInfo: null mentions: [] urls: [] hashtags: [] cashtags: [] card: null communityNote: null article: null isReply: false replyToTweetId: null replyToUserId: null isQuote: false quotedTweetId: null quotedTweet: null possiblySensitive: false conversationControl: null editTweetIds: null place: null - id: '2090515733159555570' url: https://x.com/hiilit/status/2090515733159555570 text: >- Communities are not gone , that’s right, but there’s something went wrong, sometimes the settings disappear and as administrator I could not able to access isLongForm: false lang: null createdAtMs: 1787252765000 createdAt: '2026-08-20T19:06:05.000Z' counts: likes: 25 retweets: 3 replies: 5 quotes: null bookmarks: 2 views: '13563' author: id: '2732705829' name: Maha screenName: hiilit url: https://x.com/hiilit bio: null avatarUrl: >- https://pbs.twimg.com/profile_images/2095489995717193728/Qd6GXjQo_normal.jpg avatarUrlHd: >- https://pbs.twimg.com/profile_images/2095489995717193728/Qd6GXjQo_400x400.jpg followers: 35161 following: 15015 tweetCount: 78768 verified: true verifiedType: null protected: false profileImageShape: Circle professionalCategory: null media: [] mentions: [] urls: [] hashtags: [] cashtags: [] card: null communityNote: null article: null isReply: false replyToTweetId: null replyToUserId: null isQuote: false quotedTweetId: null quotedTweet: null possiblySensitive: null conversationControl: null editTweetIds: null place: null - id: '2092115179467428129' url: https://x.com/T_z_4/status/2092115179467428129 text: >- Now that the deprecation of X Communities is final and the shift to XChat has begun, what will happen to all the valuable archives, information, and old posts created over the years? Will there be an option for admins to export community data, or will it just vanish into thin air? Anyone got updates on this? isLongForm: true lang: null createdAtMs: 1787634103000 createdAt: '2026-08-25T05:01:43.000Z' counts: likes: 17 retweets: 3 replies: 2 quotes: null bookmarks: 2 views: '13775' author: id: '1418686894691467265' name: آيَـآل screenName: T_z_4 url: https://x.com/T_z_4 bio: null avatarUrl: >- https://pbs.twimg.com/profile_images/2032281442936381440/5oGOku7c_normal.jpg avatarUrlHd: >- https://pbs.twimg.com/profile_images/2032281442936381440/5oGOku7c_400x400.jpg followers: 2146 following: 815 tweetCount: 3044 verified: true verifiedType: null protected: false profileImageShape: Circle professionalCategory: null media: [] mentions: [] urls: [] hashtags: [] cashtags: [] card: null communityNote: null article: null isReply: false replyToTweetId: null replyToUserId: null isQuote: false quotedTweetId: null quotedTweet: null possiblySensitive: null conversationControl: null editTweetIds: null place: null tweetCount: 11 fetchedAt: '2026-09-14T12:13:21.246Z' meta: requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f creditsCharged: 1 creditsRemaining: 4999 cached: false '401': description: Missing, invalid, or revoked API key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: UNAUTHORIZED message: API key required — pass it in the `x-api-key` header. requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f '402': description: Not enough credits for this request. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: INSUFFICIENT_CREDITS message: >- This request costs 1 credit, but your balance is 0. Top up to continue. requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f '404': description: Community not found / suspended. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: NOT_FOUND message: >- The requested content was not found (it may not exist, be deleted, or be private). requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f '422': description: Invalid query parameters. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: VALIDATION_ERROR message: Request validation failed requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f details: - path: url message: Required '429': description: Over the per-minute rate limit — honour `Retry-After`. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: RATE_LIMITED message: >- Rate limit exceeded — max 100 requests per 60s. Retry in ~30s. requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f '502': description: Upstream block. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: UPSTREAM_BLOCKED message: >- The source was temporarily unavailable. Please try again shortly. requestId: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f components: schemas: Error: type: object properties: error: type: object properties: code: type: string example: NOT_FOUND message: type: string example: The requested content was not found. requestId: type: string example: req_8f0c2b7e-1a2b-4c3d-9e8f-0a1b2c3d4e5f details: type: array items: type: object description: Present on validation errors. required: - code - message - requestId required: - error securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Your API key. Send it in the `x-api-key` header (or `Authorization: Bearer `). Create and manage keys from your dashboard. ````