Bluesky Post Details API
Post thread via getPostThread — nested replies[], facet links/mentions/hashtags, rich author (1 credit).
GET request to /v1/bluesky/post-details that responds with clean JSON and costs 1 credit. Pass cache=true for a free 24h cache hit; default is always fresh. Start with 100 free credits — no credit card.What is the Bluesky Post Details API?
Pass a Bluesky post URL and get the public thread (app.bsky.feed.getPostThread) — not a duplicate of a user-posts row. Beyond the list card you get: nested replies[] with per-reply author/text/engagement (depth, default 1, max 6), parentUri/rootUri/isReply so a reply is never mistaken for a root post, facet-derived links[] (full URIs — Bluesky truncates long URLs inside text), mentions[] with did, and hashtags[], post-level labels[] + langs[], and a rich author{handle,displayName,did,avatar,createdAt,labels[],verification{},verified} matching bluesky/profile (including !no-unauthenticated compliance labels). Embeds use the same normalized type namespace as user-posts (external | images | video | quote). Flat 1 credit. This is the only Captapi surface that returns Bluesky reply content.
What you get
- Nested replies[] from getPostThread (depth 0–6)
- Facet links[] / mentions[{did}] / hashtags[] — not regex over truncated text
- Rich author: verification{}, labels[], createdAt
- parentUri / rootUri / isReply + post labels[] + langs[]
Platform limits
Honest ceilings from the upstream platform surface — not Captapi bugs. Unexpected truncation here is usually the platform, not us.
- depth defaults to 1; large threads can return many reply rows in one credit.
- Bluesky has no view/play metric — engagement is likes/reposts/replies/quotes only.
Try it
Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).
Parameters
curl "https://api.captapi.com/v1/bluesky/post-details?url=https%3A%2F%2Fbsky.app%2Fprofile%2Fdanabra.mov%2Fpost%2F3mqjnjafz2s2k" \
-H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."Edit the parameters and the code updates instantly. Switch languages and hit copy.
Example response
{
"success": true,
"data": {
"platform": "bluesky",
"uri": "at://did:plc:fpruhuo22xkm5o7ttr2ktxdo/app.bsky.feed.post/3mqjnjafz2s2k",
"url": "https://bsky.app/profile/danabra.mov/post/3mqjnjafz2s2k",
"cid": "bafyreib46qdetrzwrcu35fqynwkiw6tscptkvlxcujk5f745jmzqox5jz4",
"text": "i want to do a little ✨ ama about atproto ✨ in this thread. no question is too simple\n\nif you’ve been curious about atproto but don’t know much (anything?) about it, ask any question and i’ll try to explain it in my own words.\n\n(+ would love to hear from friends who aren’t very active on bsky)",
"publishedAt": "2026-07-13T12:02:47.424Z",
"indexedAt": "2026-07-13T12:02:47.867Z",
"author": {
"handle": "danabra.mov",
"displayName": "dan",
"did": "did:plc:fpruhuo22xkm5o7ttr2ktxdo",
"avatar": "https://cdn.bsky.app/img/avatar/plain/did:plc:fpruhuo22xkm5o7ttr2ktxdo/bafkreif43mhqajnbnl62u3ezf37g6x22nd762im54thxbil4ga46eugcga"
},
"engagement": {
"likes": 340,
"reposts": 82,
"replies": 104,
"quotes": 9
},
"embed": null
}
}Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.
Response structure
A successful call returns success, cached, creditsUsed, and a data object with the following fields:
Top-level fields
platformPlatform identifier for this response (matches the endpoint's platform).uriAT URI of the post (at://did…/app.bsky.feed.post/rkey).urlbsky.app permalink for the post.cidContent ID (CID) of this post record — stable content-addressed hash.textPost text body. Long URLs may be truncated here — prefer links[].url from facets.publishedAtWhen the post record was created (ISO-8601).indexedAtWhen the AppView indexed this post (ISO-8601).embedNormalized embed: type external | images | video | quote (same namespace as user-posts).
Author
The author object contains:
handleAccount handle.displayNameDisplay name of the account. Canonical across profile endpoints (prefer over name).didDid. Example: "did:plc:fpruhuo22xkm5o7ttr2ktxdo".avatarAvatar / profile picture URL. Canonical across profile endpoints.
Engagement
The engagement object contains:
likesLike count (number).repostsRepost count.repliesNested reply tree from getPostThread. Each node matches the post shape (rich author, facets, engagement) plus its own replies[]. Depth controlled by the depth query param.quotesQuote count.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | Bluesky post URL, e.g. https://bsky.app/profile/handle/post/RKEY. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble. |
| depth | integer | No | Reply nesting levels under the post (0 = post only with no replies[], default 1, max 6). Maps to Bluesky getPostThread depth. |
| cache | boolean | No | Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits. |
Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 1 credit. Pass cache=true for a free 24h cache hit; default is always fresh.
How it works
- 1. Sign up — get 100 free credits, no card required.
- 2. Create a key from your dashboard.
- 3. Send one request to
/v1/bluesky/post-detailsand parse the JSON response.
Use cases
Thread reading
Pull a post and its nested replies[] in one call — the only Captapi path to Bluesky reply content.
Link integrity
Use links[] from facets for full URLs; Bluesky truncates long links inside text.
Compliance signals
Respect author.labels and post labels (e.g. !no-unauthenticated) before storing or displaying content.
Conversation context
parentUri / rootUri tell you whether the URL is a reply and which thread it belongs to.
Frequently asked questions
What does the Bluesky Post Details API do?+
The Bluesky Post Details API lets you fetch full metadata and key stats from a public Bluesky post using one GET request to /v1/bluesky/post-details. It returns clean JSON — no OAuth or infrastructure setup required.
How many credits does the Bluesky Post Details API cost?+
Each successful call costs 1 credit. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Failed or empty results are never charged.
Do I need a Bluesky API key or OAuth?+
No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.
Is the Bluesky Post Details API suitable for production use?+
Yes. It is a stable REST endpoint with predictable JSON and automatic retries. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Use it for analytics, monitoring, and content automation.
More Bluesky APIs
Ready to use the Bluesky Post Details API?
Sign up, grab your key, and make your first call in 60 seconds.