The open runtime
Nothing about the system is hidden.
This is the published surface of the runtime that executes engagements, so it is an honest list of what the platform can do. You are not expected to read it. Razi does the wiring during onboarding, against these same endpoints, and your office just sees the work getting done.
- Endpoints
- …
- across 8 groups of work
- Specification
- OpenAPI 3.1
- machine-readable
- Version
- …
- generated from the running code
How to read this page
You do not have to read this
Nobody at your office needs to open an API reference to hire Razi. We do the wiring during onboarding, against these same endpoints, and hand you a setup that already works.
It is here so nothing is hidden
Every capability the system has is written down in public. If a vendor cannot show you this, you are taking their word for what their software does.
Useful if you have a developer
If your team wants engagement state in your own dashboard, or wants to connect a system we have not seen before, this is the surface to build against.
What the system does
Eight groups of work, in plain terms.
Engagements
One operator running one file, from order through recording. Open it, read its state, close it.
See the endpointsSignals
Every reply, call outcome, portal event, and missed deadline that comes back in.
See the endpointsTasks
The scheduled work: a call to place, an email to send, a follow-up set for next Tuesday.
See the endpointsHandoffs
When your licensed staff take over, with the file context packaged at the moment of handoff.
See the endpointsConsent
Per channel, per party, append-only. An opt-out stops outreach and stays on the record.
See the endpointsConnectors
Register a published spec and its operations become callable work. This is how we reach your systems.
See the endpointsChannels
Your sending domains and numbers, so outreach goes out as your office, not ours.
See the endpointsAudit trail
Every decision recorded with the state it was made on, so any file can be replayed.
See the endpointsFor the developer on your team.
The full reference opens on its own page so it has room to breathe. The specification is a static file, so you can hand it to any OpenAPI tool.