Documentation
How it actually works, for the people who ask that first.
The platform services are API products and are documented as such. The business applications are documented in-product. This page says which is which, and admits where there is nothing yet rather than sending you to a stub.
The architecture
One control plane, one engine, and services that sell on their own.
Worth understanding before the API reference, because it explains why an integration against one service does not drag the rest of the platform in with it.
Platform services
The API products.
Each sells standalone, each has its own credentials, and each works alongside whatever else you run. Nothing here assumes you have adopted the rest of the family.
Rutba Send
The sending infrastructure behind receipts, password resets, invoices, payslips, and marketing campaigns — with suppression lists, bounce handling, and delivery reporting built in.
Reference documentation not published yet — ask us for the current API description and we will send it.
Rutba Media
Store master images and files once, then request any size on demand — the delivery layer behind product photos, logos, and every attachment in the family.
Reference documentation not published yet — ask us for the current API description and we will send it.
Rutba Social
Publish and schedule to X, Facebook, Instagram, LinkedIn, TikTok, and YouTube from one calendar — with approvals, per-account connections, and one API if you would rather automate it.
Rutba Studio
Video and image editors with managed template libraries that pull straight from your product catalog — so a price change updates the ad rather than invalidating it.
Reference documentation not published yet — ask us for the current API description and we will send it.
Rutba Vision
A network video recorder for IP cameras that runs entirely on your own site, with hardware-accelerated recording and detection — licensed from the portal, but never streaming your footage anywhere.
Reference documentation not published yet — ask us for the current API description and we will send it.
Business applications
Documented inside the product, where the person who needs it is. Each application carries its own help, and the search reaches across all of them because it is one system.
A public knowledge base is being built. Until it is here, support answers the questions it would have.
Integrating with your organization
Requests reach an application through the gateway, which verifies the token, asserts which organization the request belongs to, and checks the entitlement before anything reads a record. The trust centre draws that path.
Single sign-on, SCIM provisioning and audit export are available on the plans that carry them. Ask and we will send the current integration description for your deployment.
Where this page is thin, and why it says so: Most of these services do not have published reference documentation yet. Naming that is cheaper than a hub full of links to pages that turn out to be a heading and a “coming soon” — which is the version of this page that would cost us the reader entirely.
Why the services sell separately
An integration against one of these does not commit you to the rest.
Sending, storage, publishing and video are built as products rather than as features of a suite. They have their own credentials, their own plans and their own limits, and they underpin the business applications rather than being extracted from them.
Which means the sensible way to evaluate us, if you are technical, is to take one service and use it for something real. That is a much smaller decision than an ERP evaluation and it answers most of the same questions.
Need something this page does not have?
Ask for the API description, the data model, or the integration notes for the service you care about. A person answers, and there is no form in front of it.