X Engagement API: Automate Views, Likes, and Followers (2026)

Why Automate X Engagement

Most engagement tools are dashboards: you log in, paste a tweet link, pick a service, and click buy. That works for one tweet. It stops working the moment you post on a schedule, run several accounts, or want a boost to fire the instant a tweet goes live.

An engagement API turns each of those manual clicks into a request your code can make. You can queue an order the second a tweet publishes, spread delivery across a day, and read the status of every order without opening a browser. This guide covers what the XCROP Boost API does, how pricing works, and how to place and track orders on X.

What the Boost API Does

At its core, the API takes three things: a service, a link, and a quantity. The service says what you want (Views, Likes, or Followers). The link points at a single tweet for Views and Likes, or at a profile for Followers. The quantity is how many units to deliver.

Boost keeps the catalog small and focused on X:

Ids are stable, so you can store the ones you use and rely on them not shifting under you.

How Pricing Works

Services are priced per 1,000 units. XCROP quotes prices in credits, where 200,000 credits equal one US dollar. Likes are listed at 700,000 credits per 1,000, so 1,000 likes cost 700,000 credits (about $3.50), and 500 likes cost 350,000 credits.

Rather than hardcode a price, read the current rate straight from the API and compute cost as you order:

// Fetch the current Likes service and its rate
const res = await fetch('https://xcrop.io/api/v2/boost/services')
const { services } = await res.json()

const likes = services.find(s => s.id === '2')
console.log(likes.id, likes.rate) // "2" 700000  (credits per 1K)

const quantity = 2500
const cost = Math.ceil(likes.rate * (quantity / 1000))
console.log(cost) // 1750000 credits

The services endpoint is public, so you can pull the catalog and show live pricing to your own users without an API key.

Placing an Order

Ordering needs your API key in the Authorization header, the same key the rest of XCROP uses. Send the service id, the tweet link, and the quantity:

const res = await fetch('https://xcrop.io/api/v2/boost/order', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer xc_live_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    service_id: '2',
    link: 'https://x.com/user/status/123456',
    quantity: 2500,
  }),
})

const data = await res.json()
console.log(data.order_id)        // "boost_a1b2c3d4e5"
console.log(data.credits_charged) // 1750000

Credits are charged when the order is placed. If the tweet can't be actioned (for example, a protected account), the credits are refunded automatically.

Dripfeed: Delivery That Looks Natural

Dropping 10,000 likes on a tweet in one hour looks exactly like what it is. Dripfeed solves that by splitting an order into smaller batches spread across a window you choose. The same 10,000 delivered over a day reads as a tweet steadily catching on.

Add a dripfeed preset to any order that supports it:

body: JSON.stringify({
  service_id: '3',
  link: 'https://x.com/username',
  quantity: 500,
  dripfeed: '12h', // instant, 1h, 3h, 6h, 12h, 24h, 3d, 7d
})

The system handles the batch math for you: it picks batch sizes and intervals, places the first batch immediately, and schedules the rest. Credits for the full order are charged up front, and the response tells you how many batches were planned.

Use dripfeed for Followers, where a sudden jump in the count on a profile stands out the most. Views and Likes on a single tweet are less sensitive, so faster delivery is usually fine there.

Refill and Cancellation

All three services carry a refill. Views carry a lifetime refill, so a view count is not expected to drop. Likes carry a 15-day refill and Followers a 7-day refill: if the count drops after delivery, a refill tops it back up at no extra cost within that window (counted from the order date, one request per hour). Request a refill on a completed order:

await fetch('https://xcrop.io/api/v2/boost/refill', {
  method: 'POST',
  headers: { 'Authorization': 'Bearer xc_live_YOUR_KEY', 'Content-Type': 'application/json' },
  body: JSON.stringify({ orderId: 'boost_a1b2c3d4e5' }),
})

You can cancel an order while it is still pending or processing, and the undelivered portion is refunded to your balance. Once delivery is underway it cannot be reversed.

Tracking Delivery

Poll the status endpoint to watch an order move from pending to completed. For dripfeed orders it also reports batch progress and the next scheduled batch:

const res = await fetch('https://xcrop.io/api/v2/boost/status?orderId=boost_a1b2c3d4e5', {
  headers: { 'Authorization': 'Bearer xc_live_YOUR_KEY' },
})
const { order } = await res.json()
console.log(order.status)  // "in_progress"
console.log(order.remains) // 3500

A common pattern is to place an order right after publishing a tweet, then check status on a timer until remains hits zero.

Best Practices

When an Engagement API Makes Sense

If you post from one account by hand, the dashboard is enough. An API earns its keep when you are running several accounts, scheduling tweets, or wiring a boost into a posting pipeline so every tweet triggers a measured lift. In those cases, moving the work into code is the difference between an afternoon of clicking and a system that runs itself.

Ready to build it? The Boost API docs cover every endpoint, and you can browse the live catalog in the Boost dashboard.