bluesky

Search Bluesky posts

Searches public Bluesky posts by keyword and returns up to 100 posts in one page, in the unified Post shape under data.items[]: each item is { post: { id, url, content, author, engagement, flags, published_at } }. post.id is the post's record key, post.url is its bsky.app permalink, engagement.likes / comments / shares are the like, reply and repost counts, and published_at is when the author wrote it. Newest first by default; sort=top uses Bluesky's top ranking instead. Narrow with since / until, lang and author. There is no cursor: to reach older posts with the default sort=latest, call again with until set to the oldest published_at you received. A query that matches nothing returns an empty items list.

get/bluesky/search

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/bluesky/search
  • Auth: API key in header x-api-key

Query parameters

querystring required

Search terms matched against post text.

sort'latest' | 'top'

latest (newest first, the default) or top (Bluesky's own top ranking, which favours popular posts over recent ones).

sincestring

Only posts written at or after this time. ISO 8601 date (2026-09-01) or datetime with a timezone (2026-09-01T00:00:00Z); any other shape is rejected with a free 400.

untilstring

Only posts written before this time. Same format as since. Set it to the oldest published_at of your last call to fetch the next older batch; the boundary is compared to the second, so a post from that same second can repeat, and deduplicating on post.id removes it.

langstring

Only posts tagged with this language, as a code such as en, ja or ko.

authorstring

Only posts by this account: a handle such as espn.com or a did such as did:plc:.... An account that does not exist returns an empty list.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "bluesky",
  "endpoint": "/v1/bluesky/search",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  },
  "pagination": {
    "next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
    "has_more": true,
    "page_size": 30,
    "stopped_at": "known_id"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.