How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Xquik X Write API

X write actions (tweets, likes, follows, DMs)

Xquik X Write API is one of 22 APIs that Xquik publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include X Write. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 19 operations across 15 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://xquik.com.

19 operations 15 paths 18 schemas 6 DELETE1 GET3 PATCH9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://xquik.com/api/v1
Authentication
API Key, HTTP Bearer, API Key
Contact
Resource Areas
1

Authentication & Security 3

Xquik X Write API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-api-key (apiKey). It accepts HTTP bearer tokens (oauthBearer). An API key is passed in the cookie as __Host-xquik_session (cookieSession). By default, every request must be authenticated.

  • apiKey — Xquik API key passed through the x-api-key header. Xquik-Api-Key is a vendor-prefixed alias. API keys beginning with xq can also use Authorization: Bearer.
  • oauthBearer — OAuth 2.1 access token passed through Authorization: Bearer. Values beginning with xq remain Xquik API-key credentials, not OAuth tokens.
  • cookieSession — Secure Xquik browser session cookie.

Paths & Operations 19

Across 15 paths, the API surfaces 19 operations — 6 DELETE, 1 GET, 3 PATCH, 9 POST. Each is listed below with its method, path, parameters, and response codes.

X Write 19

X write actions (tweets, likes, follows, DMs)

POST
/api/v1/x/tweets
Create tweet
createTweet 1 param body → 200202400401402403409422
GET
/api/v1/x/write-actions/{id}
Get write action status
getWriteActionStatus 1 param → 200202401404429default
DELETE
/api/v1/x/tweets/{id}
Delete tweet
deleteTweet 2 params body → 200202400401402403409422
POST
/api/v1/x/tweets/{id}/like
Like tweet
likeTweet 2 params body → 200202400401402403409422
DELETE
/api/v1/x/tweets/{id}/like
Unlike tweet
unlikeTweet 2 params body → 200202400401402403409422
POST
/api/v1/x/tweets/{id}/retweet
Retweet
retweet 2 params body → 200202400401402403409422
DELETE
/api/v1/x/tweets/{id}/retweet
Unretweet
unretweet 2 params body → 200202400401402403409422
POST
/api/v1/x/users/{id}/follow
Follow user
followUser 2 params body → 200202400401402403409422
DELETE
/api/v1/x/users/{id}/follow
Unfollow user
unfollowUser 2 params body → 200202400401402403409422
POST
/api/v1/x/users/{id}/remove-follower
Remove follower
removeFollower 2 params body → 200202400401402403409422
POST
/api/v1/x/dm/{userId}
Send direct message
sendDm 2 params body → 200202400401402403409422
POST
/api/v1/x/media
Upload media
uploadMedia 1 param body → 200202400401402403404409
PATCH
/api/v1/x/profile
Update X profile
updateProfile 1 param body → 200202400401402403404409
PATCH
/api/v1/x/profile/avatar
Update profile avatar
updateAvatar 1 param body → 200202400401402403404409
PATCH
/api/v1/x/profile/banner
Update profile banner
updateBanner 1 param body → 200202400401402403404409
POST
/api/v1/x/communities
Create community
createCommunity 1 param body → 200202400401402403404409
DELETE
/api/v1/x/communities/{id}
Delete community
deleteCommunity 2 params body → 200202400401402403404409
POST
/api/v1/x/communities/{id}/join
Join community
joinCommunity 2 params body → 200202400401402403404409
DELETE
/api/v1/x/communities/{id}/join
Leave community
leaveCommunity 2 params body → 200202400401402403404409

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are XWriteAction (43 properties), GuestWalletTopupCheckoutAction (13 properties), GuestWalletCreateCheckoutAction (13 properties), XWriteActionError (12 properties). Each schema is shown below with its type and property counts.

XWritePaymentRequired
Durable failed write action with the applicable payment guidance.
XWriteActionAccount
objectnull
Connected account selected for the write.
2 properties 2 required
GuestWalletPurchaseRequest
object
User-confirmed guest wallet checkout request.
2 properties 2 required
Error
object
Error response. Default v1 returns a legacy string error code. Send xquik-api-contract: 2026-04-29 to receive the structured best-practice error object.
5 properties 1 required
GuestPaymentRequired
object
Credit error for a paid-read guest key with only its accountless guest top-up action.
8 properties 8 required
XAccountBody
object
Request body identifying an X account by username or ID.
1 property 1 required
GuestWalletCreateCheckoutAction
object
Explicit direct REST action for a new guest wallet checkout.
13 properties 13 required
XWriteActionError
object
Canonical pre-dispatch error with safe recovery guidance.
12 properties 8 required
GuestWalletTopupCheckoutAction
object
Explicit direct REST action for a guest wallet top-up.
13 properties 13 required
XWriteActionNextAction
objectnull
Exact follow-up an API client or agent should perform.
4 properties 1 required
XWriteActionRequest
object
Stable fingerprint and sanitized payload for replay checks.
2 properties 2 required
XWriteAction
object
Durable write lifecycle record. Poll statusUrl until terminal is true. Reusing the original Idempotency-Key returns this same record. Submit a new write only w…
43 properties 21 required
XWriteActionBilling
object
plannedCredits is the approved maximum. chargedCredits comes from the settled credit ledger. Pending or failed writes are not charged.
4 properties 4 required
AuthenticatedPaymentRequired
object
Authenticated credit or subscription error with confirmation-gated Stripe checkout actions.
9 properties 9 required
XWriteActionTarget
objectnull
Existing X resource targeted by the write, when applicable.
2 properties 2 required
MppPaymentRequired
object
Anonymous payment requirement for a direct MPP operation. The response includes an MPP challenge and an accountless Stripe action.
9 properties 7 required
GuestWalletAmountBounds
object
Accepted guest wallet purchase range in USD cents.
3 properties 3 required
XWriteActionResult
objectnull
Confirmed result produced by the write, when available.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xquik-api-x-write-api-openapi.yml Raw ↑

Other APIs Xquik publishes across the network.

Xquik API MCP Server
Xquik Docs MCP Server
Xquik Account API
Xquik API Keys API
Xquik Articles API
Xquik Communities API
Xquik Composition API
Xquik Draws API
Xquik Events API
Xquik Extractions API
Xquik Guest Wallets API
Xquik Lists API
Where this information came from

This is an independent, third-party profile of Xquik X Write API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.