Can think of it as two different AppViews (or just atproto apps) The DMs is did:web:api.bsky.chat#bsky_chat and the did.json is found at api.bsky.chat/.well-known/did.json And the AppView as we know it is did:web:api.bsky.app#bsky_appview api.bsky.app/.well-known/did.json
Mar 20, 2026 at 10:26 PM
app.bsky.actor.getProfile | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually proxied via the user's PDS, using service proxy headers. Authenticated requests can be used for both public and non-public endpoints.*
app.bsky.notification.getPreferences | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user's PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.*
atproto-wc · atproto-wc
Framework-agnostic ATProto web components. Content from PDS. Engagement from Constellation. Zero AppView dependency.
app.bsky.actor.searchActorsTypeahead | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user's PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.*
blacksky-algorithms/atproto
Blacksky fork of bluesky-social/atproto with AppView performance optimizations, caching, and community features
OAuth Client Implementation | Bluesky
This is a guide to implementing atproto OAuth clients "The Hard Way." Optimistically, most developers will have an SDK available for their programming language which supports OAuth, and they can simply refer to SDK documentation. This guide is intended for early adopters, SDK maintainers, or developers with more sophisticated OAuth needs. It is agnostic to whether developers are building clients to work the the app.bsky microblogging Lexicons, or implementing novel application Lexicons.
Can someone explain to me (slowly) how DM data works with atproto? More specifically now that @blackskyweb.xyz is operating its own AppView, how do my DMs show up in both apps? How do DMs differ from mutes for example.
Can someone explain to me (slowly) how DM data works with atproto? More specifically now that @blackskyweb.xyz is operating its own AppView, how do my DMs show up in both apps? How do DMs differ from mutes for example.
surprise! Shipped something on a Friday 🙂 endpoints.bsky.app is the new home for the HTTP API reference that used to live in docs.bsky.app — should be much easier to reference for quick lookups and you can even mock up / test endpoint responses in the browser!
Bluesky HTTP API Reference
endpoints.bsky.appAT Protocol apps
Apps and services on ATProto (aside from Bluesky). See “AT Protocol” collection for links related to the protocol itself, as well as “Bluesky” for Bluesky clients etc.
ATLoop
Zeens — Photography, undiluted.
A Markdown Editor on AT Protocol — Diffdown
atmoBB Forums
Your files. Your account.
Home - Blacksky Cash
