GET https://xquik.com/api/v1/styles/{id}
Free. This endpoint does not consume credits.
Retrieve one cached tweet writing profile
Call this endpoint to retrieve stored tweet samples for one writing profile. The request reads Xquik’s existing cache. It does not contact X or refresh tweets. Use an analyzed X (Twitter) username or a saved custom label as{id}. Xquik lowercases
the path value before lookup. The route does not accept a numeric database ID.
The lookup stays inside the authenticated Xquik account. Another customer can
cache the same username. You cannot read their profile.Choose the correct tweet style key
The path names the value{id}. The route reads
it as a profile key, not a numeric record ID.Encode spaces and punctuation in custom labels. Do not include
@ before an X (Twitter)
username. Keep the response’s xUsername value for later requests.Read the cached tweet style response
The response contains stored tweet text and profile metadata. It returns no generated tone summary, vocabulary list, hook score, or sentiment classification.tweetCount describes the cached writing sample. It is not the X profile’s
lifetime post count.
fetchedAt has 2 meanings. An analyzed profile records its last X fetch.
A custom profile records when Xquik saved its supplied tweet examples.
isOwnAccount is a stored snapshot. This GET request does not recompute it
after an X identity change. Set the X
identity before creating or refreshing an analyzed profile.Parse every tweet writing sample
Eachtweets[] entry follows the public style profile contract.Treat
id as a string. X Tweet IDs can exceed JavaScript’s safe integer
range. Do not cast them to number.
Custom profiles generate local sample IDs. Do not use them with X tweet lookup,
reply, like, repost, or media endpoints.Separate tweet style from Twitter analytics
This route retrieves writing samples. It does not fetch likes, replies, reposts, quotes, bookmarks, views, followers, or impressions. Use Analyze Performance when you need live engagement metrics for the cached tweets. Keep writing-style review separate from Twitter analytics for another account.Review a saved tweet style
- Call List Styles with the same credential.
- Select one returned
xUsernameprofile key. - URL-encode that value and call this endpoint.
- Store
xUsername,fetchedAt, andtweetCountwith the samples. - Review every
tweets[].textvalue before composition. - Refresh the profile through Analyze only when required.
Handle tweet style retrieval errors
The contract documents no
402 response for this cache read. A
missing balance does not block retrieval of an existing style profile.Path parameters
Headers
Sendx-api-key with an Xquik API key. OAuth clients can send a bearer token
through the Authorization header instead.Response
200 OK
401 Unauthenticated
{ "error": "unauthenticated", "message": "Missing or invalid API key" }
Authentication failed. Replace the missing or invalid credential.404 Style not found
{ "error": "style_not_found", "message": "No cached style found for this username" }
No matching cache key exists for this Xquik account. Call List Styles first.
Analyze the X (Twitter) username when no profile exists.429 Rate limited
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 1 }
Too many requests. Wait for Retry-After, then retry once.How do I retrieve a cached tweet writing style?
List styles, copy onexUsername, then send it as {id}. This endpoint
returns the saved tweet text without refreshing the X profile.Can I retrieve another account’s Twitter writing style?
Yes, after your Xquik account analyzes that public username. You cannot read a style profile cached by another Xquik customer.Does get style return Twitter analytics?
No. It returns tweet writing samples and cache metadata. Use Analyze Performance for current likes, replies, reposts, and views.Why does get style return 404?
The credential cannot access a matching lowercase username or label. Call List Styles, check the exact key, then analyze or save the profile.Related. List Styles lists profile
keys. Delete Style removes a cached profile.
Response examples
200 example
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "not_found", "message": "Resource not found." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }