The following two instances include a phrase in which a word appears to be missing. I think it might be "define", but I'm uncertain. The translations don't mention the scope at all, as far as I can tell.
Atproto HTTP API methods [define] each scope and implement a particular set of Lexicons.
|
Atproto HTTP API methods each scope and implement a particular set of Lexicons. The AT Protocol's API system, [XRPC](/specs/xrpc), is essentially a thin wrapper around HTTPS. For example, a call to: |
Atmosphere HTTP API methods [define] each scope and implement a particular set of Lexicons, so Lexicons must include valid query parameters, request bodies, and response bodies as appropriate.
|
Lexicons are authored in JSON — you can find examples in the [Lexicon Guide](/guides/lexicon). Atmosphere HTTP API methods each scope and implement a particular set of Lexicons, so Lexicons must include valid query parameters, request bodies, and response bodies as appropriate. Each Lexicon, in turn, becomes a permission scope — in other words, `app.bsky.feed.post` is an AT record format, a web endpoint, and a granular permission all at once. |
The following two instances include a phrase in which a word appears to be missing. I think it might be "define", but I'm uncertain. The translations don't mention the scope at all, as far as I can tell.
atproto-website/src/app/[locale]/guides/lexicon/en.mdx
Line 33 in f98505f
atproto-website/src/app/[locale]/guides/permission-sets/en.mdx
Line 64 in f98505f