Get a Bluesky profile and its posts

Profile

GET /v1/bluesky/profile takes handle. That value is a handle (alice.bsky.social) or a DID (did:plc:...). username is an alias. The parameter is required.

The recorded request uses the bsky.app handle.

1curl -G "https://api.socialscrape.dev/v1/bluesky/profile" \2  -H "x-api-key: $SOCIALSCRAPE_API_KEY" \3  --data-urlencode "handle=bsky.app"

1import os2import requests34params = {5    "handle": "bsky.app",6}7res = requests.get(8    "https://api.socialscrape.dev/v1/bluesky/profile",9    headers={"x-api-key": os.environ["SOCIALSCRAPE_API_KEY"]},10    params=params,11)12body = res.json()1314if body["ok"]:15    print(body["data"])16else:17    print(body["error"]["code"], body["error"]["message"])

1const url = new URL("https://api.socialscrape.dev/v1/bluesky/profile");2url.search = new URLSearchParams({3  "handle": "bsky.app"4}).toString();5const res = await fetch(url, {6  headers: { "x-api-key": process.env.SOCIALSCRAPE_API_KEY! },7});8const body = await res.json();910if (body.ok) {11  console.log(body.data);12} else {13  console.error(body.error.code, body.error.message);14}

data

is a profile. platform is bluesky. You get id, handle, name, bio, avatar_url, banner_url, url, verified, is_private, external_url and links. created_at is set when the profile has one.

stats.followers, stats.following and stats.posts

are the counts. stats.likes and stats.views are null when the profile has no such totals.

extra

on the recorded profile includes did, associated, indexed_at, pinned_post_uri, status and verification. Keep extra.did if you will call the posts endpoint next. The reference says a DID is the faster lookup. user_id is an alias of handle on the posts route, so you can pass the DID in handle (or as user_id) without inventing a second parameter.

Errors are invalid_params and not_found. An unknown handle is not_found. Do not retry it.

Posts

GET /v1/bluesky/profile/posts is a paged feed of that user's posts. handle is required, same shape as the profile call. cursor pages forward. Changing nothing but the cursor continues the same feed.

1curl -G "https://api.socialscrape.dev/v1/bluesky/profile/posts" \2  -H "x-api-key: $SOCIALSCRAPE_API_KEY" \3  --data-urlencode "handle=bsky.app"

1import os2import requests34params = {5    "handle": "bsky.app",6}7res = requests.get(8    "https://api.socialscrape.dev/v1/bluesky/profile/posts",9    headers={"x-api-key": os.environ["SOCIALSCRAPE_API_KEY"]},10    params=params,11)12body = res.json()1314if body["ok"]:15    print(body["data"])16else:17    print(body["error"]["code"], body["error"]["message"])

1const url = new URL("https://api.socialscrape.dev/v1/bluesky/profile/posts");2url.search = new URLSearchParams({3  "handle": "bsky.app"4}).toString();5const res = await fetch(url, {6  headers: { "x-api-key": process.env.SOCIALSCRAPE_API_KEY! },7});8const body = await res.json();910if (body.ok) {11  console.log(body.data);12} else {13  console.error(body.error.code, body.error.message);14}

data.items

are posts. Each has id, url, text, published_at, author, media, hashtags, mentions and stats. stats.likes and stats.comments are filled when Bluesky sends them. stats.views is commonly null. stats.shares is the shared field. Bluesky's own counters also land in extra: repost_count, quote_count, cid, uri and image_alts. Use extra.uri and extra.cid if you store the AT Protocol identity of the post. url is the bsky.app link.

cursor and has_more

tell you whether to continue. Send the cursor back unchanged. Stop when has_more is false. Each page costs 1 credit. Pagination describes the loop. parent is the profile the feed belongs to.

A single post, including embed content and threaded replies, is GET /v1/bluesky/post with the post URL (bsky.app/profile/<handle>/post/<rkey>). Replies come back in extra.replies on that call. The feed endpoint is the list. The post endpoint is one record.