Check the store marker
/api/settings/evidence/probeThe same three-valued probe startup takes. A store that answers with somebody else's store marker, or with none, locks; a store that does not answer at all does not, because silence is not evidence of loss.
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 POST "https://example.com/api/settings/evidence/probe"{ "state": "string", "explanation": "string", "expectedStoreId": null, "foundStoreId": null, "since": null, "consecutiveFailures": 0, "uploadsAllowed": true, "locked": true, "storeDescription": "string"}Set evidence limits PUT
Per-file, per-report and per-deployment caps, and direct delivery. No round trip: none of these repoints a store. Zero means no limit on the two totals; the per-file cap is enforced three times and cannot be zero.
List ban reasons GET
The reasons a moderator picks from when banning, kicking, unbanning or turning a join request down; usedFor says which actions offer each one. In button order, switched-off ones included with isActive false. Seeded with a plain default set the first time anybody asks, so the first case file can be written without inventing a list first. reasonAlwaysRequired says whether the actions other than a ban need a reason too.