Endpoint reference

The first question about any endpoint here is which credential opens it, so that is how this reference is split. Of the 102 routes below, 20 are reachable with an integration key, an embed key, or no credential at all; the other 82 require a signed-in dashboard session.

The split

Each endpoint is listed in full wherever it appears: auth, parameters, a request example, a response example per branch, the status codes, and a runnable curl. A drift test checks this reference against the routers in the repository in both directions, so a shipped route cannot go undocumented and a documented route cannot outlive its handler.