Documentation
Build on Velora
Everything you need to build on Velora. Get an OAuth token, pick the surface that matches what you are building — REST, events, webhooks or the chat socket — and ship. Start at the top; the pages below it get more specific, not more important.
Press ⌘K (or Ctrl K) anywhere in the portal to search.
Step one
Start here
Four pages, in the order the questions arrive: what the API looks like, which surface you want, how to get a token, and what that token is allowed to do.
The surfaces
Moving data in and out
Velora exposes four ways to reach a channel. Read the endpoint list first — it is generated from the controllers, so it is the one page that cannot drift from what the server enforces.
Going further
Specialised surfaces and operational detail
Bot identities, template tokens, the limits you will hit in production, and the exhaustive endpoint reference.
Worked examples
Integration guides
End-to-end walkthroughs rather than reference: a whole integration, from first request to shipped feature.
By resource
API Reference
Jump straight into the full reference at the resource you care about. Counts are the number of documented endpoints in that section.
Developer Discord