KIDUART school ERP
School ERP integrations

Connect the tools your school already runs

Fee gateways, parent messaging, school sign-in accounts, online classes, gate devices and a REST API. Live connectors ship today; guided ones are switched on with our team; roadmap items stay labelled as roadmap not dressed up as features.

Book a Free DemoView API Docs

Three honest labels, not one wall of logos

Every connector on this page carries its real status

Most vendor integration pages show a grid of brand marks and let you assume everything works. If an integration decides whether KIDUART fits your school, you should know where it stands before the demo not after signing.

Available now

13

Implemented in the product and configured from your own school settings.

Connected with our team

5

Built and working, but switched on with us during onboarding because it needs your credentials, admin consent or hardware.

On the roadmap

5

Not in the product yet. Listed openly so you can plan around it instead of discovering it after signing.

The full directory

Connectors grouped by the job they do

Filter by status or jump to the category you care about. Every connector page explains the hop-by-hop flow, who holds the credentials, what your school has to bring, and which modules the data actually lands in.

Fee payments

Online fee collection that reconciles back into the fee book, so the receipt and the ledger never disagree.

Messaging and notifications

How notices, fee reminders and attendance alerts actually reach parents WhatsApp, SMS, email and app notifications.

Sign-in and identity

Let staff and students use the school accounts they already have, without a second password.

Online classes and meetings

Launch a class or a parent meeting from the timetable instead of pasting links into a group.

Campus devices and tracking

Biometric punches and bus locations arriving in the same attendance and transport records your staff already use.

Files, data and developer access

Document storage, exports your accountant can open, and the REST API your IT team can build against.

Under the hood

What actually happens when a connector runs

The same five rules apply whether it is a fee payment, an absence SMS or a gate punch. This is the part a school should ask every vendor about, because it decides who is liable when something goes wrong.

  1. The account stays in your name

    Your Razorpay merchant ID, your SMS sender ID, your WhatsApp number, your Workspace domain. We never resell a shared account, so your settlement, credits and sender reputation stay yours.

  2. Credentials are encrypted per school

    Keys and tokens are stored encrypted against your school record, isolated from every other school on the platform, and can be rotated or removed by you without touching anything else.

  3. Work is queued, not blocked

    Messages and notifications go through a queue, so a slow provider never freezes the screen a clerk is working on and a failed send can be retried instead of vanishing.

  4. The provider confirms it independently

    Payment and delivery callbacks are signature-verified before anything is written. A fee is closed on a confirmed webhook, not on a browser redirect that could be faked or lost.

  5. It lands in the module, with a trail

    The payment appears on the fee record, the message on the communication log, the punch on the attendance register each with a record of what happened, so a dispute has an answer.

Said out loud

What we are not connected to

These come up in almost every demo. Rather than leave you to discover them later, here is the list with what we do instead.

  • Cashfree, PayU, Paytm and PhonePeOnline fee collection runs on Razorpay or Stripe today. No other gateway is wired in, whatever a feature list elsewhere might suggest.
  • Tally and QuickBooksFinance data leaves as Excel, CSV or PDF for your accountant. There is no direct accounting connector.
  • DigiLocker, Aadhaar eKYC and UDISEDocument and identity numbers can be stored on the student record, but there is no live government API connection.
  • Board result portalsReport cards are generated inside KIDUART. Results are not pushed to or pulled from board portals.
  • School-subscribed outbound webhooksWe handle incoming provider webhooks. Letting your systems subscribe to KIDUART events is still on the roadmap.

For your IT team

Build your own with the REST API

Schools connect attendance devices, their public website, or a reporting warehouse. Your developers work against versioned REST endpoints using a scoped API key never a shared staff login with rate limits and request logging on every call.

  • Versioned REST endpoints under a stable /api/v1 base path
  • Managed API keys with scoped permissions you can rotate
  • Signature-verified webhooks from payment and messaging providers
  • Published endpoint reference and error contract for your team
View API Docs
// Students in one class, read-only key
const res = await fetch(
'https://api.kiduart.com/api/v1/students?classId=8A',
{ headers: {
'x-api-key': 'kd_live_•••'
} });
// → { success: true, data: [...], meta: {...} }

Before you commit

Integration questions schools ask

Do we have to change our payment gateway or SMS provider?

No. KIDUART connects to the accounts you already run Razorpay or Stripe for fees, Twilio, MSG91 or Amazon SNS for SMS, your own WhatsApp Business number, your own email domain. You keep the commercial relationship and the pricing you negotiated.

Who pays for SMS, WhatsApp and payment gateway charges?

You do, on your own provider accounts. That is deliberate: your SMS credits, WhatsApp conversation charges and gateway fees stay visible and negotiable to you instead of being marked up inside a subscription.

Is there an extra charge for each integration?

No. Connecting a gateway, a messaging provider or your school accounts is part of the platform. What you pay outside KIDUART is whatever your provider bills you directly.

What does 'guided setup' mean on this page?

It means the integration is built and working, but it is switched on with our team during onboarding because it needs credentials, admin consent or hardware from your side a Zoom app, Microsoft tenant consent, or an attendance machine at the gate.

We already have biometric machines and bus GPS. Do we replace them?

No. Tell us the make and model. Punches can flow into the attendance register through a device key, and vehicle locations can sit against the route and vehicle records, so the hardware you already bought becomes useful to the office.

Can our own website or internal system talk to KIDUART?

Yes, through the REST API. Your developer gets a scoped API key rather than a shared staff login, works against versioned endpoints, and the key can be rotated or revoked without disturbing anyone's account.

Do you integrate with Tally, Cashfree, PayU or DigiLocker?

Not today. Finance data leaves as Excel, CSV or PDF for your accountant, and online fee collection runs on Razorpay or Stripe. We list what is not connected on this page rather than letting a wall of logos imply otherwise.

If we leave, do we lose the data these integrations created?

No. Payments, messages, documents and attendance records are your school's data and can be exported. Integration credentials are yours to revoke at your provider the same day.

Fee paymentsMessaging and notificationsSign-in and identityOnline classes and meetingsCampus devices and trackingFiles, data and developer access
Live demo

Tell us which tools your school cannot give up

Bring your payment gateway, messaging provider, school accounts and gate devices to the demo. We will show exactly how each one connects and say plainly if it does not yet.

Request a Demo Contact Sales

  • 30-minute walkthrough

    Booked around your school hours

  • Run on your own data

    Your fee heads, classes and staff roles

  • No card, no lock-in

    Nothing is charged to see the product