npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

tweetapi-node

v2.4.0

Published

Node.js and TypeScript SDK for TweetAPI's Twitter/X data and account API

Readme

TweetAPI Node.js SDK

tweetapi-node is the Node.js and TypeScript SDK for TweetAPI. It includes typed methods for profiles, tweets, lists, communities, Spaces, direct messages, search, and authenticated account actions.

Install

npm install tweetapi-node

Quick start

import TweetAPI from "tweetapi-node";

const client = new TweetAPI({ apiKey: "YOUR_API_KEY" });

// Get a user profile
const user = await client.user.getByUsername({ username: "elonmusk" });
console.log(user.data.followerCount);

// Search tweets
const results = await client.explore.search({ query: "bitcoin", type: "Latest" });

// Get followers with pagination
const followers = await client.user.getFollowers({ userId: "USER_ID" });
const nextPage = await client.user.getFollowers({
  userId: "USER_ID",
  cursor: followers.pagination.nextCursor!,
});

Create an API key with 100 included requests. No credit card is required.

SDK behavior

  • TypeScript types cover request parameters, response models, pagination, and errors.
  • paginate() and paginatePages() are async generators. The optional maxPages setting limits how many pages they request.
  • Requests retry up to three times by default after a 429 response, a 5xx response, or a network error. Retry settings are configurable.
  • client.profile.updateUsername() is not automatically retried because username changes are not safe to replay.
  • client.interaction.acceptFollowRequest() and denyFollowRequest() are never automatically retried. Follow-request reads keep the configured retry behavior.
  • RateLimitError.retryAfter and client.rateLimitInfo expose rate-limit delay information from the last 429 response.
  • Error classes distinguish validation, authentication, permission, not-found, rate-limit, server, and connection failures.
  • The client has no runtime dependencies and uses native fetch on Node.js 18 or newer.
  • The package provides ESM, CommonJS, and TypeScript declaration builds.

API reference

User

| Method | Description | |--------|-------------| | client.user.getByUsername({ username }) | Get user profile by username | | client.user.getByUsernames({ usernames }) | Get multiple users by usernames (comma-separated) | | client.user.getByUserId({ userId }) | Get user profile by ID | | client.user.getByUserIds({ userIds }) | Get multiple users by IDs (comma-separated) | | client.user.getTweets({ userId }) | Get a user's tweets | | client.user.getTweetsAndReplies({ userId }) | Get a user's tweets and replies | | client.user.getFollowing({ userId }) | Get who a user follows | | client.user.getFollowers({ userId }) | Get a user's followers | | client.user.getVerifiedFollowers({ userId }) | Get verified followers | | client.user.getSubscriptions({ userId }) | Get user's subscriptions | | client.user.getFollowingV1({ userId }) | Get following (v1, supports count) | | client.user.getFollowersV1({ userId }) | Get followers (v1, supports count) | | client.user.getFollowingIds({ userId }) | Get following user IDs | | client.user.getFollowersIds({ userId }) | Get follower user IDs | | client.user.checkFollow({ subjectId, targetId }) | Check follow relationship | | client.user.aboutAccount({ username }) | Get account transparency info |

Profile

| Method | Description | |--------|-------------| | client.profile.update({ authToken, name, bio, location, website }) | Update authenticated profile fields | | client.profile.updateUsername({ authToken, password, username }) | Change the authenticated account username | | client.profile.avatar({ authToken, media }) | Update profile avatar from image URL or base64 data | | client.profile.banner({ authToken, media }) | Update profile banner from image URL or base64 data | | client.profile.removeBanner({ authToken }) | Remove the profile banner | | client.profile.setPrivacy({ authToken, isPrivate }) | Make the account public or private |

Tweet

| Method | Description | |--------|-------------| | client.tweet.getDetailsAndConversation({ tweetId }) | Get tweet details and replies | | client.tweet.getDetailsByIds({ ids }) | Get multiple tweets by IDs (max 200) | | client.tweet.getRetweets({ tweetId }) | Get who retweeted a tweet | | client.tweet.getQuotes({ tweetId }) | Get quote tweets | | client.tweet.translate({ tweetId, dstLang }) | Translate a tweet |

Post

| Method | Description | |--------|-------------| | client.post.createPost({ authToken, text, proxy, replyOption }) | Create a tweet | | client.post.createPostQuote({ authToken, text, attachmentUrl, proxy, replyOption }) | Create a quote tweet | | client.post.createPostWithMedia({ authToken, text, media, proxy }) | Create a tweet with media | | client.post.replyPost({ authToken, text, tweetId, proxy }) | Reply to a tweet | | client.post.replyPostWithMedia({ authToken, text, tweetId, media, proxy }) | Reply with media | | client.post.deletePost({ authToken, tweetId }) | Delete a tweet |

// Restrict who can reply to a new tweet
await client.post.createPost({
  authToken: "TWITTER_AUTH_TOKEN",
  text: "Shipping with TweetAPI",
  proxy: "host:port@user:pass",
  replyOption: { mode: "verified_accounts" },
});

// Reuse caller-managed Twitter media by media_id_string
await client.post.createPostWithMedia({
  authToken: "TWITTER_AUTH_TOKEN",
  text: "Direct media ID",
  media: [{ media_id: "TWITTER_MEDIA_ID" }],
  proxy: "host:port@user:pass",
});

// Or let TweetAPI upload media from URL/base64
await client.post.createPostWithMedia({
  authToken: "TWITTER_AUTH_TOKEN",
  text: "Uploaded media",
  media: [{ url: "https://example.com/image.jpg", type: "image/jpeg" }],
  proxy: "host:port@user:pass",
});

Interaction

| Method | Description | |--------|-------------| | client.interaction.favoritePost({ authToken, tweetId }) | Like a tweet | | client.interaction.unfavoritePost({ authToken, tweetId }) | Unlike a tweet | | client.interaction.retweet({ authToken, tweetId }) | Retweet | | client.interaction.deleteRetweet({ authToken, tweetId }) | Remove retweet | | client.interaction.bookmark({ authToken, tweetId }) | Bookmark a tweet | | client.interaction.deleteBookmark({ authToken, tweetId }) | Remove bookmark | | client.interaction.follow({ authToken, userId }) | Follow a user | | client.interaction.unfollow({ authToken, userId }) | Unfollow a user | | client.interaction.getFollowRequests({ authToken, cursor?, count?, proxy? }) | List incoming follow-request IDs | | client.interaction.acceptFollowRequest({ authToken, userId, proxy? }) | Accept one incoming follow request | | client.interaction.denyFollowRequest({ authToken, userId, proxy? }) | Deny one incoming follow request | | client.interaction.addMemberToList({ authToken, listId, userId }) | Legacy alias for adding user to list | | client.interaction.removeMemberFromList({ authToken, listId, userId }) | Legacy alias for removing user from list | | client.interaction.getNotifications({ authToken }) | Get notifications | | client.interaction.getUserAnalytics({ authToken }) | Get account analytics |

The supplied authToken determines whose incoming requests you manage. All three methods accept an optional proxy in the existing host:port@user:pass format. Listing defaults to cursor "-1" and count 100; count must be an integer from 1 to 100. The response is a PaginatedResponse<string> with precise digit-string IDs, no profiles or total count, and null terminal cursors. An empty list is a successful response.

List requests, then select one requester to review:

const authToken = "TWITTER_AUTH_TOKEN";
const page = await client.interaction.getFollowRequests({ authToken, count: 20 });
console.log(page.data); // Requester IDs; keep these as strings.

// Fetch another page only when one exists.
if (page.pagination.nextCursor !== null) {
  const nextPage = await client.interaction.getFollowRequests({
    authToken,
    count: 20,
    cursor: page.pagination.nextCursor,
  });
  console.log(nextPage.data);
}

After reviewing the list, choose either acceptance or denial for one digit-only userId. Replace "REQUESTER_USER_ID" with the selected ID; do not convert it to a number.

const result = await client.interaction.acceptFollowRequest({
  authToken: "TWITTER_AUTH_TOKEN",
  userId: "REQUESTER_USER_ID",
});
console.log(result.data.action); // "accept_follow_request"
console.log(result.data.metadata?.user_id);

To deny the selected request instead:

await client.interaction.denyFollowRequest({
  authToken: "TWITTER_AUTH_TOKEN",
  userId: "REQUESTER_USER_ID",
});

Both mutations return ActionResponse, with data.id and data.metadata.user_id equal to the supplied ID, a timestamp, success: true, and action "accept_follow_request" or "deny_follow_request". Neither operation has an idempotency guarantee. A timeout or connection failure leaves the outcome uncertain: inspect the pending requests and account state to reconcile the result before considering a manual retry. Do not automatically replay these mutations after an error.

List

| Method | Description | |--------|-------------| | client.list.getDetails({ listId }) | Get list details | | client.list.getTweets({ listId }) | Get tweets in a list | | client.list.getMembers({ listId }) | Get list members | | client.list.getFollowers({ listId }) | Get list followers | | client.list.create({ authToken, name, description, isPrivate }) | Create a list | | client.list.addMember({ authToken, listId, userId }) | Add user to list | | client.list.removeMember({ authToken, listId, userId }) | Remove user from list |

const list = await client.list.create({
  authToken: "TWITTER_AUTH_TOKEN",
  name: "Research",
  description: "Accounts to monitor",
  isPrivate: true,
});

await client.list.addMember({
  authToken: "TWITTER_AUTH_TOKEN",
  listId: list.data.id,
  userId: "USER_ID",
});

Profile examples

await client.profile.update({
  authToken: "TWITTER_AUTH_TOKEN",
  name: "TweetAPI Research",
  bio: "Twitter/X data workflows",
  website: "https://tweetapi.com",
});

await client.profile.updateUsername({
  authToken: "TWITTER_AUTH_TOKEN",
  password: "TWITTER_PASSWORD",
  username: "NEW_USERNAME",
});

await client.profile.avatar({
  authToken: "TWITTER_AUTH_TOKEN",
  media: { url: "https://example.com/avatar.jpg", type: "image/jpeg" },
});

await client.profile.banner({
  authToken: "TWITTER_AUTH_TOKEN",
  media: { data: "BASE64_IMAGE_DATA", type: "image/png" },
});

await client.profile.removeBanner({
  authToken: "TWITTER_AUTH_TOKEN",
});

await client.profile.setPrivacy({
  authToken: "TWITTER_AUTH_TOKEN",
  isPrivate: true,
});

Community

| Method | Description | |--------|-------------| | client.community.getDetails({ communityId }) | Get community details | | client.community.getTweets({ communityId, sortBy }) | Get community tweets | | client.community.getMembers({ communityId }) | Get community members | | client.community.search({ query }) | Search communities | | client.community.createPost({ authToken, text, communityId, proxy }) | Post in community | | client.community.createPostWithMedia({ ... }) | Post with media in community | | client.community.createQuote({ authToken, text, attachmentUrl, communityId, proxy }) | Quote tweet in community | | client.community.createQuoteWithMedia({ ... }) | Quote tweet with media in community | | client.community.replyPost({ ... }) | Reply to community post | | client.community.replyPostWithMedia({ ... }) | Reply with media in community | | client.community.join({ authToken, communityId }) | Join a community | | client.community.leave({ authToken, communityId }) | Leave a community |

await client.community.createQuote({
  authToken: "TWITTER_AUTH_TOKEN",
  text: "Relevant for this community",
  attachmentUrl: "https://x.com/example/status/TWEET_ID",
  communityId: "COMMUNITY_ID",
  proxy: "host:port@user:pass",
});

await client.community.createQuoteWithMedia({
  authToken: "TWITTER_AUTH_TOKEN",
  text: "Community quote with media",
  attachmentUrl: "https://x.com/example/status/TWEET_ID",
  communityId: "COMMUNITY_ID",
  media: [{ media_id: "TWITTER_MEDIA_ID" }],
  proxy: "host:port@user:pass",
});

Space

| Method | Description | |--------|-------------| | client.space.getById({ spaceId }) | Get Space details | | client.space.getStreamUrl({ mediaKey }) | Get Space HLS stream URL |

Explore

| Method | Description | |--------|-------------| | client.explore.search({ query, type }) | Search tweets/users/photos/videos |

Auth

| Method | Description | |--------|-------------| | client.auth.login({ username, password, proxy, country }) | Log in and get auth tokens |

country is the ISO 3166-1 alpha-2 code for the proxy's public egress IP (for example, "US"). It must match the IP used for the complete login attempt. Pass twoFactorSecret when the account uses TOTP-based 2FA.

X Chat (encrypted DMs)

| Method | Description | |--------|-------------| | client.xchat.setup({ authToken, userId, pin }) | Initialize encrypted DMs | | client.xchat.getConversations({ authToken }) | List encrypted conversations | | client.xchat.send({ authToken, recipientId, message }) | Send encrypted message | | client.xchat.getHistory({ authToken, conversationId }) | Get conversation history | | client.xchat.canDm({ authToken, userIds }) | Check DM availability |

Unencrypted DMs

| Method | Description | |--------|-------------| | client.dm.sendDm({ authToken, conversationId, text, proxy }) | Send a DM | | client.dm.getDmPermissions({ authToken, recipientIds }) | Check DM permissions | | client.dm.getInboxInitialState({ authToken }) | Get inbox state | | client.dm.getInboxTrusted({ authToken, cursor }) | Get trusted inbox | | client.dm.getInboxUntrusted({ authToken, cursor }) | Get message requests | | client.dm.getConversation({ authToken, conversationId }) | Get conversation messages | | client.dm.getDmUserUpdates({ authToken, cursor }) | Get DM user updates | | client.dm.acceptConversation({ authToken, conversationId }) | Accept a conversation |

Pagination

Use the paginate() and paginatePages() helpers to iterate through all pages automatically:

import TweetAPI, { paginate, paginatePages } from "tweetapi-node";

const client = new TweetAPI({ apiKey: "YOUR_API_KEY" });

// Iterate individual items across all pages
for await (const user of paginate(
  (cursor) => client.user.getFollowers({ userId: "USER_ID", cursor }),
)) {
  console.log(user.username);
}

// Iterate full pages (access page-level data)
for await (const page of paginatePages(
  (cursor) => client.explore.search({ query: "bitcoin", type: "Latest", cursor }),
  { maxPages: 5 },  // optional: limit number of pages
)) {
  console.log(`Got ${page.data.length} results`);
  console.log(`Next cursor: ${page.pagination.nextCursor}`);
}

Both helpers accept a function that returns a PaginatedResponse. Use them with resource methods whose responses contain data and pagination.nextCursor.

Retries

By default, the client retries these failures:

  • A 429 response waits for the API's retryAfter duration, capped by maxRetryDelay.
  • A 5xx response uses exponential backoff with jitter.
  • A timeout or connection failure uses the same exponential backoff.
  • Other 4xx responses fail without a retry.

The defaults are three retries, a 1-second initial delay, a backoff multiplier of 2, and a 30-second maximum delay.

profile.updateUsername(), interaction.acceptFollowRequest(), and interaction.denyFollowRequest() always make one attempt, even when global retries are enabled. interaction.getFollowRequests() retains normal retries and works with both pagination helpers.

// Customize retry behavior
const client = new TweetAPI({
  apiKey: "YOUR_API_KEY",
  retry: {
    maxRetries: 5,           // default: 3
    initialRetryDelay: 2000, // default: 1000ms
    backoffMultiplier: 3,    // default: 2
    maxRetryDelay: 60000,    // default: 30000ms
  },
});

// Disable retries entirely
const client = new TweetAPI({
  apiKey: "YOUR_API_KEY",
  retry: false,
});

Rate-limit state

After a 429 response, the SDK exposes the last known rate limit state:

console.log(client.rateLimitInfo);

Error handling

The client throws subclasses of TweetAPIError. Retryable errors reach your code after the configured retries are exhausted.

import TweetAPI, {
  TweetAPIError,
  AuthenticationError,
  RateLimitError,
  NotFoundError,
  ValidationError,
  ServerError,
  ConnectionError,
} from "tweetapi-node";

try {
  const user = await client.user.getByUsername({ username: "elonmusk" });
} catch (error) {
  if (error instanceof RateLimitError) {
    console.log(`Rate limited. Retry in ${error.retryAfter}s`);
  } else if (error instanceof NotFoundError) {
    console.log("User not found");
  } else if (error instanceof AuthenticationError) {
    console.log("Invalid API key");
  } else if (error instanceof ValidationError) {
    console.log(`Bad request: ${error.message}`);
  } else if (error instanceof ServerError) {
    console.log("API is having issues, try again later");
  } else if (error instanceof ConnectionError) {
    console.log("Network error — check your connection");
  } else if (error instanceof TweetAPIError) {
    console.log(`Error [${error.code}]: ${error.message}`);
  }
}

Every error includes:

  • code: API error code, such as "ACCOUNT_SUSPENDED" or "RATE_LIMIT"
  • statusCode: HTTP status code
  • message: human-readable error message
  • details: additional context such as a field, reason, or retryAfter value

Configuration

const client = new TweetAPI({
  apiKey: "YOUR_API_KEY",       // Required
  baseUrl: "https://...",       // Optional (default: https://api.tweetapi.com)
  timeout: 30000,               // Optional (default: 30000ms)
  retry: {                      // Optional (default: { maxRetries: 3 })
    maxRetries: 3,
    initialRetryDelay: 1000,
    backoffMultiplier: 2,
    maxRetryDelay: 30000,
  },
});

Requirements

  • Node.js 18+ (uses native fetch)
  • TypeScript 5+ (for type definitions)

Links

License

MIT

TweetAPI is a third-party service and is not affiliated with X Corp.