Check the Bluesky account
/api/settings/bluesky/checkFind the account from the handle, sign in (the saved session when it still works, otherwise a renewal of the sign-in with Bluesky, or the app password, at most once every 10 minutes and 20 times a day), and read the account's display name and whether it is marked as automated. Never posts and writes nothing to the account. Answers 200 with what it found, a refusal included. While Bluesky is limiting Modbot nothing is sent and the stored result is returned.
Needs the ManageSettings permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/api/settings/bluesky/check"{ "handle": null, "appPasswordStored": true, "posting": true, "canPost": true, "check": null, "limitedUntil": null, "signInAfter": null, "signInWithBluesky": false, "signedInWithBluesky": false, "postTags": "", "pinNextEvent": false, "lineupOn": false, "lineupDay": 1, "lineupHour": 12, "lineupTimeZone": null, "klipyKey": ""}Update Bluesky settings PUT
Save the handle, an app password, Posting, the tags every calendar post ends with (PostTags, at most 5, each at most 64 characters; empty clears them), PinNextEvent (keep the next calendar date's post pinned on the profile), LineupOn, LineupDay (0 is Sunday), LineupHour (0 to 23) and LineupTimeZone (an IANA name, empty for UTC): once a week the next seven days' public dates go out as one post, or any of them. Only an app password is taken (four groups of four letters or digits, made in Bluesky's settings); anything else is refused with "Use an app password.". It is kept encrypted and never returned. Saving the handle or the app password clears what the last Check found, and posts wait until Check passes again. Posting on needs a Check that passed. Needs the `ManageSettings` permission.
Start signing in with Bluesky POST
Only when the public address is https with no port. Finds the account from the handle (the one given, or the stored one) both ways, asks the account's sign-in server for a sign-in (PAR, PKCE, DPoP, with Modbot's own signing key) and answers the address of Bluesky's sign-in page. Bluesky sends the browser back to /api/bluesky/callback, which only the person who started may finish, and only for this account. Nothing is saved but the waiting sign-in, good for ten minutes. Needs the `ManageSettings` permission.