Features
Solutions
Free tools
Resources

iVake joins the stack you already run

Nobody changes their bank or accounting software because they changed platforms. iVake connects to what you already run; for anything specific to you there is a documented API.

What comes in, and what goes back out

Most connections run in one direction, and it is worth knowing which before your IT team asks.

Into iVake

DOCVerified documents from DigiLocker
PAYPayment confirmations and settlement files
ATTPunches from biometric and RFID devices
LEADEnquiries from Meta, Google and your website
CALLCall outcomes and recordings from the dialer
iVakeONE RECORD

Out of iVake

FINDay book and ledgers to Tally or Zoho Books
GOVReturns for AICTE, UGC and AISHE
CREDIssued marksheets back to DigiLocker and ABC
MSGWhatsApp, SMS and email to families
BIScheduled extracts to your reporting tool
Your stackUNCHANGED

Anything not on this list is reachable through the REST API and webhooks.

Every connection, by category

Six groups. Each lands against the student record it belongs to.

Payments

Razorpay
PayU
Cashfree
HDFC gateway
ICICI gateway
UPI & NEFT refs

Money settles into your accounts exactly as it does today. iVake records the transaction against the student and reconciles the gateway settlement file against the fee ledger every day.

Government & regulatory

DigiLocker
APAAR / ABC
NAD
AICTE returns
UGC / AISHE
State portals

DigiLocker documents arrive with the issuer’s signature intact, so verification is a consistency check rather than a judgement call. Issued marksheets and certificates go back into the student’s DigiLocker and Academic Bank of Credits.

Finance & accounting

Tally
Zoho Books
Bank statements
GST reports
TDS & payroll filing
Custom ledger export

One export your auditor recognises.

Communication

WhatsApp Business
DLT-registered SMS
Transactional email
IVR & missed call
Dialers & call centre
App push

Reach families where they actually read. Call recordings and outcomes from a connected dialer attach to the applicant record.

Campus hardware & identity

Biometric devices
RFID & smart cards
Bus GPS trackers
Google Workspace
Microsoft Entra ID
SAML SSO

Devices and directories you already own.

Learning & analytics

Moodle
Google Classroom
Teams & Meet
Power BI
Looker Studio
Read replica

Teaching tools and your own BI stack.

Everything in the platform is in the API

Your website, your app, your dialer and your reporting tool read and write through documented endpoints. Nothing is locked behind an export button.

  • REST API over leads, applications, students, fees, attendance and results.
  • Webhooks on state change, so your systems react instead of polling.
  • Scoped keys with per-endpoint permissions and rate limits.
  • Sandbox before anything touches live data.
  • Bulk import and full export in open formats, at any time.
POST /v1/leads
curl -X POST https://api.ivake.com/v1/leads \  -H "Authorization: Bearer $IVAKE_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "name": "Ananya R.",    "phone": "+919876543210",    "programme": "btech-cse",    "campus": "main",    "source": {      "channel": "meta_ads",      "campaign": "cse-july",      "cost_paise": 41200    },    "consent": { "whatsapp": true }  }'

Response · 184 ms

HTTP/1.1 201 Created{  "id": "lead_7Q2mK4nR",  "stage": "enquiry",  "counsellor": { "name": "Priya S.", "queue": "btech-cse" },  "duplicate": { "found": false, "checked": ["phone", "email"] }}

Returns the lead id, the assigned counsellor and the deduplication result. A lead.stage_changed webhook fires on every subsequent movement through the funnel.

Getting your existing data in

The two questions every IT team asks first.

What can you import from our current system?

Students and their academic history. Staff records. Fee structures, with balances paid and outstanding. Attendance history, results, and enquiry records with their original source and stage. Documents come across as files attached to the right record. Anything with a defined structure can be mapped. The work is agreeing the mapping, not the transfer itself.

Our data is in spreadsheets, not a system.

That is the usual case. We work from your actual files and agree a mapping. Then we run a trial import into a test copy and show you the result before anything touches live data. Messy data gets cleaned during mapping, not after go-live.

See iVake running on your own data

Share your fee structure and programmes before the call, or sample data with student names removed. We set them up, so you see your own institution on screen rather than a demo account.

  • 45 minutes, your data. Not a generic tour of features.
  • Migration mapped on the call. We show exactly where your current records land.
  • A written rollout plan within two working days, with phases, owners and dates.
  • No pressure to switch everything at once. Most schools and colleges start with one department or one intake.