POST
/api/v2/followers/orderCreate a Followers Engine shipment. Body takes handle, tier, geo, and curve. Returns tracking ID and ETA.
Product · API and Resellers
Programmatic everything.
The REST API has been live since 2015. v2 is stable since 2022. Order follower shipments, engagement suites, and impressions packages through clean JSON, receive webhook events when things ship or refill, and white label the output under your own brand if you are reselling. SDKs for Node, Python, Go, and PHP, all MIT licensed on GitHub.
v2
API version, stable since 2022
300/min
Reseller tier rate limit
4
Official SDKs, MIT licensed
99.95%
Enterprise tier SLA
- Live since
- 2015, v2 since 2022
- Endpoints
- 18, all JSON REST
- Webhook security
- HMAC SHA256
- Sandbox
- Full parity environment
What it isThe same engine,
The same engine,
exposed as JSON.
The Twitterz API is the Followers Engine, the Engagement Suite, and the Impressions product behind a REST interface. Nothing privileged, nothing hidden. The same infrastructure the marketing site routes orders through is exposed directly to developers and resellers through a handful of endpoints.
We run the API because about thirty percent of our GMV comes through resellers who operate their own panels on top of our fulfillment. The alternative for a reseller is to scrape checkout flows from upstream panels, which is fragile and violates most upstream terms. A real API solves that cleanly. Stable contract, versioned endpoints, signed webhooks, and a sandbox that mirrors production behavior without shipping real orders.
The API is also how internal tools, affiliate dashboards, and the customer dashboard on app.twitterz.net talk to the fulfillment stack. So every improvement on the API benefits direct customers too. The uptime on the API is the uptime on the whole service, which is why it is on the public status page.
Endpoints, v2
Six core routes, the rest are helpers.
Full reference at docs.twitterz.net/api/v2. The routes below cover over ninety percent of production traffic.
POST
/api/v2/engagement/orderCreate an Engagement Suite shipment. Body takes tweet URL, tier, and optional ratio override. Returns tracking ID.
POST
/api/v2/impressions/orderCreate an Impressions shipment. Body takes handle or tweet URL, tier, scope (per tweet or account wide), drip.
GET
/api/v2/orders/:idFetch order status. Returns state (pending, shipping, complete, warranty active), delivered count, refill count.
GET
/api/v2/audit/:handleRun the five filter audit on a handle. Returns fake ratio, filter breakdown, recommended cleanup actions.
POST
/api/v2/webhooksRegister a webhook URL for event delivery. Signed with HMAC SHA256. Events include order.complete, refill.triggered, audit.ready.
// Create a followers shipment
POST https://api.twitterz.net/v2/followers/order
Authorization: Bearer twz_live_...
{
"handle": "@yourbrand",
"tier": "growth",
"geo": "usa",
"curve": "drip_72h"
}
API tiers
Developer, Reseller, Enterprise.
Tiers scale by monthly GMV, rate limit, and support channel. Reseller adds white label and margin pricing. Enterprise adds a custom SLA with uptime penalties and dedicated infrastructure.
Starter API access, up to $2,000 monthly GMV, 60 req/min
$500/mo
requests, real and warrantied
$500$800
one time, never recurring
- ✓Full catalog endpoints
- ✓60 requests per minute
- ✓Webhook delivery events
- ✓Sandbox environment
- ✓Slack support channel
- ✓No reseller margin
Margin program, up to $20,000 monthly GMV, 300 req/min
$2K/mo
requests, real and warrantied
$2,000$3,500
one time, never recurring
- ✓Full catalog + white label panel
- ✓300 requests per minute
- ✓Webhook + push events
- ✓Reseller margin 15% to 25%
- ✓Named account engineer
- ✓Priority pool on peak windows
Unlimited volume, SLA, dedicated infrastructure
Custom
requests, real and warrantied
Talk—
one time, never recurring
- ✓Custom rate limits
- ✓Dedicated strategist + engineer
- ✓Private webhook routing
- ✓99.95% SLA with penalties
- ✓Quarterly reviews
- ✓Outline Technologies escalation path
Developer questions
What builders ask at integration.
Eight questions we answer at almost every integration. More in the docs at docs.twitterz.net. Direct support at [email protected].
- What is the Twitterz API?
- The Twitterz API is the programmatic interface to the full product catalog. Resellers, agencies, and tool builders use it to ship Followers Engine, Engagement Suite, and Impressions orders without touching the marketing site. Launched 2015, currently on v2, stable since 2022.
- Do I need to be a reseller to use it?
- No. The Developer tier is open to any builder running tools or internal automation. Reseller tier adds white label panel access and margin pricing, which is useful only if you are marking up and reselling to end customers. Most agencies run on Developer for client work and move to Reseller when the client count justifies the white label.
- What does the reseller margin look like?
- Reseller tier buyers pay roughly 15 to 25 percent below the public direct price, depending on monthly GMV. The margin is the difference you retain between our wholesale and your retail. Most resellers mark up between 30 and 60 percent on top of our wholesale, which preserves the 15 to 25 percent margin net even after competing with the public page.
- Can I resell under my own brand?
- Yes on the Reseller and Enterprise tiers. The white label panel strips Twitterz branding from order confirmations, dashboards, and email receipts. Warranty is still backed by us but under your brand to your end customer. About 40 percent of Reseller tier buyers run fully white label. The rest surface Twitterz as the upstream.
- What is the rate limit math?
- Developer is 60 requests per minute per key. Reseller is 300 per minute. Enterprise is custom, typically 1,000 to 5,000 per minute with burst allowance. All tiers have a 10 second hard timeout on creates so long running operations return a tracking ID immediately and complete asynchronously via webhook.
- Do webhook events come with retries?
- Yes. Failed webhook deliveries retry with exponential backoff across 24 hours, up to 8 attempts. Each attempt is signed with an HMAC signature in the X-Twitterz-Signature header. Verify the signature before processing to prevent replay. The signing secret rotates on request or every 90 days automatically.
- Is there a sandbox?
- Yes. The sandbox environment at sandbox.twitterz.net mirrors v2 with deterministic responses and no real shipment. Useful for integration testing. Sandbox orders complete in 30 seconds rather than 24 hours, which lets you integration test warranty flows in minutes instead of months.
- Do you have SDKs?
- Official SDKs for Node, Python, Go, and PHP. All four are on the GitHub org at github.com/twitterz. Each SDK handles request signing, retries, webhook signature validation, and the common error cases. Source code is MIT licensed so you can fork if our abstractions do not fit your stack.
Q01
Q02
Q03
Q04
Q05
Q06
Q07
Q08
Keep reading
Neighboring services and guides.
Followers Engine
The product the API routes shipment requests to.
Engagement Suite
Accessible via /engagement/order on the API.
Impressions & Bookmarks
The monetization product, exposed via /impressions/order.
For Agencies
Most API customers are agencies. The solutions lens on the same pattern.
Affiliate program
Lower commitment than Reseller. 20% recurring on referred orders.
Status page
API uptime is the service uptime. Live metrics.
Eleven years of one API.
v2 is stable since 2022. Breaking changes go through a 12 month deprecation window. The contract is the contract.
Crypto checkout · No password · 24 month warranty