Remove the Bluesky account
/api/settings/blueskyForget the handle, the app password or the sign-in with Bluesky, the session and what Check found, and turn Posting off. Nothing on Bluesky is changed: posts already sent stay.
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
curl -X DELETE "https://example.com/api/settings/bluesky"{ "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": ""}Get Bluesky settings GET
The Bluesky account Modbot posts as: its handle, whether an app password is saved, Posting, and what the last Check found. The app password and the session are never returned. Needs the `ManageSettings` permission.
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.