twitterapi-io

What This Skill Does

The twitterapi-io skill provides a robust interface for interacting with Twitter/X via the TwitterAPI.io REST API. It acts as an integration layer for OpenClaw agents, enabling them to perform both read and write operations on the platform. The skill supports all 59 available endpoints, allowing for advanced automation tasks such as searching for tweets, fetching user metadata, posting content, managing likes and retweets, following accounts, and even handling direct messages. It emphasizes the use of v2 endpoints, which are the current standard, ensuring compatibility with modern Twitter authentication flows.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/dorukardahan/twitterapi-io

Ensure you have obtained your API key from the TwitterAPI.io dashboard. For secure usage, store your key in a .env file or a secure environment configuration rather than hardcoding it into your scripts to prevent exposure in shell history.

Use Cases

• Social Media Monitoring: Automatically search and aggregate tweets related to specific keywords or hashtags for sentiment analysis or market research.
• Account Management: Automate engagement tasks such as liking relevant content, retweeting industry updates, or following key figures in your domain.
• Content Pipeline: Schedule or publish tweets directly from your AI agent, including media uploads via the v2 upload endpoints.
• Data Acquisition: Extract detailed user profiles or follower lists to build databases for networking or outreach campaigns.

Example Prompts

1. "Find the 10 most recent tweets containing the hashtag #OpenClaw and provide a brief summary of the sentiment."
2. "Search for the user profile of 'elonmusk' and list their current bio and follower count."
3. "Like the tweet with ID 1234567890 and send a direct message to the author thanking them for the update."

Tips & Limitations

• API Inconsistency: Note that while user_login_v2 returns a field called login_cookie, you must map this value to a field named login_cookies (plural) in all subsequent write-action requests.
• Cost Awareness: Be mindful of credit usage. Most write actions cost between 200-300 credits. Since the API charges a minimum of 15 credits per call, ensure your requests are batched where possible to maximize value.
• Rate Limiting: Your request speed (QPS) is tied to your account balance. Free tier users are limited to 1 request every 5 seconds, while higher-tier users benefit from up to 20 QPS.
• Version Control: Always prioritize v2 endpoints. V1 is deprecated, and cookies between versions are incompatible.