API reference
Every endpoint, the permission it needs, and whether an API key may call it — read from
https://api.proofbell.com/v1/openapi.json as you load this page, so it cannot drift from the running
API.
Request and response bodies are not described. Validation is done with schemas that live in the code rather than in decorated classes, so nothing can currently derive the shapes automatically — and a hand-written copy would be wrong within a month. What is here is complete and accurate: paths, methods, permissions, scopes and error shape. What is missing is missing on purpose rather than by oversight, and tell us if you are generating a client, because that is the thing that would move it up the list.
Loading the document…