REST API Overview

The Xquik REST API v1 provides programmatic access to X data and automation. Endpoints are organized into these categories:

Monitors & Events

Create monitors, retrieve events, manage webhooks

Draws & Extractions

Run giveaway draws, extract tweet data

X Data

User lookups, tweet search, trends, media downloads

X Write Actions

Post tweets, like, retweet, follow, DM, profile updates

Account & Billing

Account info, API keys, drafts, styles, subscriptions

Base URL

https://xquik.com/api/v1

All endpoints are served over HTTPS only. Plain HTTP requests receive a 301 redirect to HTTPS. Always use the full base URL - there is no shorthand or versioned subdomain.

OpenAPI spec

The full API specification is available as an OpenAPI 3.1 document:

https://xquik.com/openapi.json

Use this with any OpenAPI-compatible tool (Postman, Insomnia, Swagger UI) or to generate client libraries. The spec follows RFC 9727 service discovery conventions.

Authentication

Pass your API key via the x-api-key header:

x-api-key: xq_YOUR_KEY_HERE

Generate keys from your dashboard. See Authentication for full details on key format, dual auth endpoints, and security best practices.

Machine Payments Protocol

32 X-API endpoints also accept anonymous MPP payments. The server returns a 402 challenge; your client pays via Tempo (USDC) and retries with a payment credential. No API key needed. See the MPP overview for eligible endpoints and pricing.

First request

Copy-paste this to verify your API key works:

curl -s https://xquik.com/api/v1/account \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

Response:

{
  "plan": "active",
  "monitorsAllowed": 1,
  "monitorsUsed": 0,
  "currentPeriod": {
    "start": "2026-02-01T00:00:00.000Z",
    "end": "2026-03-01T00:00:00.000Z",
    "usagePercent": 0
  }
}

Replace xq_YOUR_KEY_HERE with your actual API key from the dashboard. If you get 401, double-check that the header name is x-api-key (lowercase) and the key starts with xq_.

Rate limits

Tier	Methods	Limit
Read	GET, HEAD, OPTIONS	120 per 60s
Write	POST, PUT, PATCH	30 per 60s
Delete	DELETE	15 per 60s

Exceeding limits returns 429 Too Many Requests with a Retry-After header. See the Rate Limits guide for backoff implementations in multiple languages.

Conventions

IDs are strings

All IDs are returned as strings representing bigint values. Always treat IDs as opaque strings - never parse them as numbers:

{ "id": "123456789" }

Timestamps are ISO 8601 UTC

All timestamps use ISO 8601 format in UTC. Store and compare timestamps as strings or parse them into proper date objects:

{ "createdAt": "2026-02-24T10:30:00.000Z" }

Errors follow a consistent format

All errors return a JSON body with an error field containing a machine-readable error code:

{ "error": "error_code" }

Common errors:

Status	Code	Meaning
400	`invalid_input`	Request body failed validation
401	`unauthenticated`	Missing or invalid API key
402	`no_subscription`	No active subscription
402	`usage_limit_reached`	Monthly usage limit exceeded
404	`not_found`	Resource does not exist
429	—	Rate limited — retry with backoff
502	`x_api_unavailable`	X data source temporarily unavailable — retry

See Error Handling for the full error code list and handling strategies.

Cursor-based pagination

Platform endpoints
X endpoints

Events, draws, extractions, and drafts use cursor-based pagination. When more results exist, the response includes hasMore: true and a nextCursor value:

{
  "events": [],
  "hasMore": true,
  "nextCursor": "MjAyNi0wMi0yNFQxMDozMDowMC4wMDBa..."
}

Pass nextCursor as the after query parameter to fetch the next page:

curl "https://xquik.com/api/v1/events?after=MjAyNi0wMi0yNFQxMDozMDowMC4wMDBa..." \
 -H "x-api-key: xq_YOUR_KEY_HERE"

X data endpoints (/x/*) use a different pagination shape. When more results exist, the response includes has_next_page: true and a next_cursor value:

{
  "tweets": [],
  "has_next_page": true,
  "next_cursor": "DAABCgABGRnYttk__..."
}

Pass next_cursor as the cursor query parameter to fetch the next page:

curl "https://xquik.com/api/v1/x/tweets/search?query=xquik&cursor=DAABCgABGRnYttk__..." \
 -H "x-api-key: xq_YOUR_KEY_HERE"

Cursors are opaque strings - do not decode or construct them manually. Monitors, webhooks, and API keys return up to 200 items without pagination.

Event types

Monitor events

Used across monitors, webhooks, and events:

Type	Description
`tweet.new`	Original tweet posted by the monitored account
`tweet.quote`	Quote tweet posted by the monitored account
`tweet.reply`	Reply posted by the monitored account
`tweet.retweet`	Retweet posted by the monitored account
`follower.gained`	New follower gained by the monitored account
`follower.lost`	Follower lost by the monitored account

Integration events

Integrations (Telegram push notifications) support 3 additional event types for job completion:

Type	Description
`draw.completed`	Giveaway draw finished with winners selected
`extraction.completed`	Extraction job completed with results ready
`extraction.failed`	Extraction job failed

Next steps

Error Handling

Handle errors gracefully with retries and fallbacks.

Rate Limits

Understand limits and implement backoff strategies.

Workflows

End-to-end examples: monitors, events, and webhooks.

X Data Endpoints

User lookups, tweet search, trends, and media downloads.

X Write Actions

Post tweets, like, retweet, follow, DM, and more.

Monitors

Track X accounts and receive real-time events.

Overview

X API

X Write

Trends

Radar

Account

API Keys

Credits

X Accounts

Monitors

Events

Webhooks

Integrations

Draws

Extractions

Compose

Drafts

Styles

Support

Monitors & Events

Draws & Extractions

X Data

X Write Actions

Account & Billing

​Base URL

​OpenAPI spec

​Authentication

​Machine Payments Protocol

​First request

​Rate limits

​Conventions

​Event types

​Monitor events

​Integration events

​Next steps

Error Handling

Rate Limits

Workflows

X Data Endpoints

X Write Actions

Monitors

Base URL

OpenAPI spec

Authentication

Machine Payments Protocol

First request

Rate limits

Conventions

Event types

Monitor events

Integration events

Next steps