One by Service Yantra · Integrations
It works with the systems you're already running.
One by Service Yantra is built to be the system of record for your property operations — not a walled-off tool sitting next to your ERP, your helpdesk, or your building sensors. Every work order, photo, checklist and invoice exists as structured data from day one, ready to export. Below, we've drawn an honest line: what actually connects today, and what's still ahead on the roadmap.
Built to be honest about what's connected.
Enterprise evaluations tend to fall apart over surprises found late. This page exists so that doesn't happen here.
Your data is never held hostage.
Evidence files, CSV and PDF export are part of the platform subscription from day one — no export fee, no friction designed to keep you locked in.
A roadmap item is always labelled ROADMAP.
We don't show anything as live unless it's actually running today. The numbers in the directory below are real counts — never inflated to look bigger.
A named engineer, not a sales funnel.
Questions about connectors go to platform engineers directly, through a documented channel. Integration scoping happens during onboarding, not as a separate sales motion.
What connects, and what's next.
Each status below reflects the current build, not an intention. Data export works today. The API and system connectors are on the roadmap, and marked as such.
Evidence files & data export
Every work order, photo, checklist and invoice inside One by Service Yantra can be exported as a structured evidence file — CSV, PDF evidence packs, scheduled exports. It's built for RBI inspection trails, FSSAI hygiene logs and NABH readiness — dates, photos, responsible parties, all in a single file.
Data & reporting
One API (REST)
A documented, versioned REST API spanning sites, assets, work orders, SLA events and invoices — token-based, read access first, DPDP Act-conscious by design. We'll publish it once v1 is genuinely live and documented, not before.
Data & reporting
Your ERP or accounting stack
GST-compliant invoice and spend data feeding into whatever finance system you already run — through scheduled export today, and through the API once One API v1 ships. No ERP logo wall here — the connector is a data contract, not a marketing badge.
Finance & ERP
Single sign-on (SAML / OIDC)
Sign in to One by Service Yantra through your own identity provider, so branch users and HQ teams simply inherit your existing access rules.
Identity & access
Ticketing & ITSM
Raise and track work orders directly from your existing helpdesk or ITSM queue, with status webhooks keeping both systems aligned.
Ticketing & ITSM
BMS & IoT sensors
Building-management alerts and sensor thresholds — temperature, water level, DG status — trigger work orders automatically, moving from alert to a routed technician without anyone making a call.
Buildings & sensors
Don't see your system on this list? Custom connectors get scoped during onboarding, and our existing data export already covers most of what a one-off connector would do anyway. This systems-fit review is built into the Yantra Inspection itself.
One API. The platform, made addressable.
Every visit across the network writes a structured, photo-evidenced record as a natural by-product of the work itself — the checklist pulled from your subscribed scope, run through One Field, visible inside One Command. One API exposes that same record: the 70-item asset-inventory schema that the Yantra Inspection builds for each site becomes the schema your own systems can read. It ships documented and versioned, or it doesn't ship at all.
- Documented and versioned — no undocumented endpoints anywhere in the contract path
- Token-based authentication, with access scoped per permission
- Read scopes come first; write scopes get enabled per contract
- Compliance teams export their own evidence files, with no ticket required
GET /v1/work-orders?site=DEL-014&status=completed
{
"id": "WO-24817",
"site": "DEL-014",
"sla_met": true,
"photo_evidence": ["before.jpg", "after.jpg"],
"invoice_ref": "INV-2026-0042",
"amount_inr": 4850
}Illustrative preview of the roadmap schema. Synthetic data — no client systems, no live endpoint.
Asked by evaluators.
Can we actually get our data out?
Yes — today. Evidence files, CSV and PDF evidence packs export directly from One by Service Yantra, included in the subscription, with no export toll and no lock-in. The REST API that would make these same records addressable programmatically is on the roadmap, and it'll publish only once it's live, documented and versioned.
Do you integrate with our ERP, helpdesk or BMS?
GST-compliant invoice and spend data already exports into your finance system today. Deeper API, ITSM and BMS/IoT connectors sit on the roadmap, clearly labelled as such above. We won't present a connector as live before it actually is.
Is there a REST API right now?
One API v1 is on the roadmap. Once it's live, it'll ship documented and versioned, with token-based access and read scopes first. We don't publish endpoints ahead of them existing.
How does integration scoping actually work?
The systems-fit review happens as part of the Yantra Inspection, and custom connectors get scoped during onboarding. Connector questions go straight to platform engineers, through a documented path — not a sales pipeline.
How is our data handled?
Data is treated with a DPDP Act-conscious posture across both branch and personnel records, and your estate's data stays ring-fenced to your contract. Export is available to you on demand.
Will it fit your stack? Let the inspection tell you.
The Yantra Inspection includes a systems-fit review — covering what connects today, what a connector would eventually handle, and how your evidence gets out either way — all before you're asked to commit to anything.