Bluesky reference
Bluesky API guide
Read public accounts and posts using handles, DIDs and post URIs. Keep the original post author separate from the account that reposted it.
Quickstart
Start with Bluesky
Read public accounts and posts using handles, DIDs and post URIs. Keep the original post author separate from the account that reposted it.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Resolve an account
The returned id is the account DID; store it alongside the current handle. Parameters and current cost →
curl "https://www.monocrawl.com/v1/bluesky/profile?handle=bsky.app" \ -H "x-api-key: mn_your_key_here"
2. Read the account feed
Supply handle or user_id. Keep each post’s at:// URI and is_repost flag when present. Parameters and current cost →
curl "https://www.monocrawl.com/v1/bluesky/user/posts?handle=bsky.app&limit=25" \ -H "x-api-key: mn_your_key_here"
3. Inspect a post
Use a returned post URL or at:// post URI. The author can differ from the feed owner. Parameters and current cost →
curl "https://www.monocrawl.com/v1/bluesky/post?url=https%3A%2F%2Fbsky.app%2Fprofile%2Fespn.com%2Fpost%2F3lqdfq7fkvm2g" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Identity | A handle can change; store the DID alongside it. Post IDs are at:// URIs, not decimal numbers. Endpoint reference → |
| Feed owner versus author | Supply handle or user_id. A repost preserves the original author and reports is_repost, so do not attribute every feed row to the owner. Endpoint reference → |
| Search ordering | sort is top or latest. Keep sort and query with the opaque cursor; ranking can change between requests. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| Keyword discovery | search | Select latest or top and preserve the query and cursor. |
| Stable account identity | profile | A DID and a handle serve different purposes; preserve both. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Posts and media
Accounts and audiences
Search and discovery
Operations
Bluesky
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Bluesky
4 operationsElsewhere
The same registry, other shapes
- Bluesky overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=bluesky— the same rows to your code at runtime, for 0 credits.