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

vee3-io X Twitter API

The x-twitter API from vee3-io — 14 operation(s) for x-twitter.

vee3-io X Twitter API is one of 27 APIs that vee3-io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include X / Twitter. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 15 operations across 14 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against the base URL https://api.vee3.io.

15 operations 14 paths 23 schemas 3 DELETE7 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.vee3.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

vee3-io X Twitter API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 15

Across 14 paths, the API surfaces 15 operations — 3 DELETE, 7 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

x-twitter 15
GET
/v1/x-twitter/connected-accounts
Get X connected accounts
get_x_connected_accounts_v1_x_twitter_connected_accounts_get → 200
POST
/v1/x-twitter/bookmarks
Create X bookmark
create_x_bookmark_v1_x_twitter_bookmarks_post body → 200422
GET
/v1/x-twitter/bookmarks
Get X bookmarks
get_x_bookmarks_v1_x_twitter_bookmarks_get 4 params → 200422
POST
/v1/x-twitter/posts
Create X post
create_x_post_v1_x_twitter_posts_post body → 201422
DELETE
/v1/x-twitter/bookmarks/{post_id}
Delete X bookmark
delete_x_bookmark_v1_x_twitter_bookmarks__post_id__delete 3 params → 200422
DELETE
/v1/x-twitter/posts/{post_id}
Delete X post
delete_x_post_v1_x_twitter_posts__post_id__delete 3 params → 200422
POST
/v1/x-twitter/posts/edit
Edit X post
edit_x_post_v1_x_twitter_posts_edit_post body → 201422
POST
/v1/x-twitter/posts/reply
Reply to X post
reply_to_x_post_v1_x_twitter_posts_reply_post body → 201422
POST
/v1/x-twitter/reposts
Repost X post
repost_x_post_v1_x_twitter_reposts_post body → 200422
DELETE
/v1/x-twitter/reposts/{post_id}
Unrepost X post
unrepost_x_post_v1_x_twitter_reposts__post_id__delete 3 params → 200422
GET
/v1/x-twitter/user-info
Get X user info
get_x_user_info_v1_x_twitter_user_info_get 2 params → 200422
GET
/v1/x-twitter/tweet-info
Get X tweet info
get_x_tweet_info_v1_x_twitter_tweet_info_get 1 param → 200422
GET
/v1/x-twitter/tweet-replies
Get X tweet replies (latest)
get_x_tweet_replies_v1_x_twitter_tweet_replies_get 2 params → 200422
GET
/v1/x-twitter/user-timeline
Get X user timeline
get_x_user_timeline_v1_x_twitter_user_timeline_get 3 params → 200422
GET
/v1/x-twitter/search
Search X
search_x_v1_x_twitter_search_get 3 params → 200422

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are GetXUserInfoResult (20 properties), ReplyToXPostRequest (17 properties), CreateXPostRequest (14 properties), GetXTweetInfoResult (12 properties). Each schema is shown below with its type and property counts.

ReplyToXPostResult
object
4 properties 4 required
XConnectedAccountSummary
object
5 properties 4 required
SearchXResult
object
4 properties 1 required
RepostXPostRequest
object
3 properties 1 required
XBookmarkMutationResult
object
3 properties 3 required
DeleteXPostResult
object
3 properties 3 required
EditXPostRequest
object
7 properties 1 required
GetXBookmarksResult
object
4 properties
EditXPostResult
object
4 properties 4 required
HTTPValidationError
object
1 property
UnrepostXPostResult
object
3 properties 3 required
ValidationError
object
5 properties 3 required
GetXUserInfoResult
object
20 properties 3 required
ReplyToXPostRequest
object
17 properties 1 required
CreateXPostPollOptions
object
3 properties 2 required
CreateXPostRequest
object
14 properties
CreateXPostResult
object
4 properties 4 required
CreateXBookmarkRequest
object
3 properties 1 required
GetXTweetInfoResult
object
12 properties 2 required
GetXConnectedAccountsResult
object
1 property 1 required
GetXUserTimelineResult
object
6 properties 1 required
RepostXPostResult
object
4 properties 4 required
GetXTweetRepliesResult
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vee3-io-x-twitter-api-openapi.yml Raw ↑

Other APIs vee3-io publishes across the network.

vee3-io Agent Downloads API
vee3-io Agent Uploads API
vee3-io Clerk API
vee3-io Cron API
vee3-io Domains API
vee3-io Files API
vee3-io Google Maps API
vee3-io Google Search API
vee3-io Google Search Console API
vee3-io Google Trends API
vee3-io Health API
vee3-io Image Generation API
Where this information came from

This is an independent, third-party profile of vee3-io X Twitter 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.