Twitterapi Io

twitterapi-io

Use the installed twitterapi-io CLI for read-only twitterapi.io access.

This skill exists to make common twitterapi.io reads simple and low-noise instead of rebuilding custom API calls each time.

Quick rules

• Use this skill only for reads.
• Do not improvise posting/like/reply/delete flows.
• Prefer compact JSON output by default.
• Use --raw only when you actually need full API objects.
• Prefer the official docs links in references/links.md when validating endpoint behavior.

Installation preference

Prefer an installed CLI over hardcoded script paths.

Preferred install:

pipx install git+https://github.com/ropl-btc/twitterapi-io-cli.git

Fallback inside a repo checkout:

pip install .

After install, use:

twitterapi-io

Commands

Show built-in help

twitterapi-io help

Authenticate once

twitterapi-io auth --api-key YOUR_KEY

You can also use env:

export TWITTERAPI_IO_KEY='YOUR_KEY'

Fetch one tweet

twitterapi-io tweet --url 'https://x.com/jack/status/20'

or:

twitterapi-io tweet --id 20

Fetch one user

twitterapi-io user --username OpenAI

Fetch recent tweets for a user

twitterapi-io user-tweets --username OpenAI --limit 10

Include replies:

twitterapi-io user-tweets --username OpenAI --limit 10 --include-replies

Fetch replies to a tweet

twitterapi-io replies --url 'https://x.com/jack/status/20' --limit 20

Optional unix-time filters:

twitterapi-io replies --id 20 --since-time 1741219200 --until-time 1741305600 --limit 20

Fetch quote tweets

twitterapi-io quotes --id 20 --limit 20

Fetch thread context

twitterapi-io thread-context --id 20 --limit 40

Fetch mentions for a user

twitterapi-io mentions --username OpenAI --limit 20

Advanced search

twitterapi-io search --query 'AI agents -filter:replies' --from-user OpenAI --within-time 24h --max-tweets 50

Use Top results when needed:

twitterapi-io search --query 'AI agents' --queryType Top --max-pages 2

Use explicit unix-time operators when needed:

twitterapi-io search --query '$BTC' --since-time 1741219200 --until-time 1741305600 --max-tweets 50

Workflow

1. Read references/links.md if you need the underlying official twitterapi.io docs links. 2. Ensure the twitterapi-io CLI is installed. 3. Ensure the API key exists via auth or env. 4. Use tweet, user, user-tweets, replies, quotes, thread-context, mentions, or search as needed. 5. Keep reads narrow and intentional.

Expected outputs

The CLI returns JSON. Parse it instead of scraping human text.

Default output is compact and low-noise. Use --raw when full endpoint payloads are actually needed.

Files

• Package repo: https://github.com/ropl-btc/twitterapi-io-cli
• Compatibility wrapper: scripts/twitterapi_io.py
• Official docs links: references/links.md
• Config storage: ~/.config/twitterapi-io/config.json

When to stop and ask

Stop and ask before:

• adding write/posting capabilities
• adding login-cookie flows
• adding broad/high-cost scraping defaults
• changing how API key storage works

twitterapi.io docs

Core official docs used for this CLI:

• Introduction: https://docs.twitterapi.io/introduction
• Documentation index: https://docs.twitterapi.io/llms.txt
• Authentication: https://docs.twitterapi.io/authentication
• Get Tweets by IDs: https://docs.twitterapi.io/api-reference/endpoint/get_tweet_by_ids
• Get User Info: https://docs.twitterapi.io/api-reference/endpoint/get_user_by_username
• Get User Last Tweets: https://docs.twitterapi.io/api-reference/endpoint/get_user_last_tweets
• Get Tweet Replies: https://docs.twitterapi.io/api-reference/endpoint/get_tweet_replies
• Get Tweet Quotations: https://docs.twitterapi.io/api-reference/endpoint/get_tweet_quotations
• Get Tweet Thread Context: https://docs.twitterapi.io/api-reference/endpoint/get_tweet_thread_context
• Get User Mentions: https://docs.twitterapi.io/api-reference/endpoint/get_user_mentions
• Advanced Search: https://docs.twitterapi.io/api-reference/endpoint/tweet_advanced_search

Important notes from docs:

• API auth uses the x-api-key header.
• GET /twitter/tweets uses tweet_ids.
• GET /twitter/user/info uses userName.
• GET /twitter/user/last_tweets accepts userName or userId, plus includeReplies and cursor.
• GET /twitter/tweet/replies accepts tweetId, optional sinceTime, untilTime, and cursor.
• GET /twitter/tweet/quotes accepts tweetId and cursor.
• GET /twitter/tweet/thread_context accepts tweetId and cursor.
• GET /twitter/user/mentions appears to require userName on the live endpoint; use username input here and verify against official docs if behavior changes.
• GET /twitter/tweet/advanced_search accepts query, queryType, and cursor.
• Advanced search and timeline-style endpoints paginate with has_next_page + next_cursor.
• For search date filters, prefer since_time:, until_time:, and within_time: operators.