Ivake joins your stack. It does not ask you to rebuild it
Nobody changes their bank or their accounting software because they changed platforms. Ivake connects to what you already run. For anything specific to you, there is a documented API.
How data moves
What comes in, and what goes back out
Ivake is not a walled garden. Most connections run in one direction, and it is worth knowing which before your IT team asks.
Into Ivake
Out of Ivake
Anything not on this list is reachable through the REST API and webhooks.
Payments
Money settles into your accounts, exactly as it does today
Razorpay
HDFC gateway
ICICI gatewayIvake records the transaction against the student. Every day it reconciles the gateway settlement file against the fee ledger. Finance sees matched and unmatched entries, not two spreadsheets to compare by hand.
Government & regulatory
Verified documents in, issued credentials out
DigiLocker documents arrive with the issuer's signature intact. Verification becomes a consistency check rather than a judgement call. Marksheets and certificates you issue can be pushed back into the student's DigiLocker and Academic Bank of Credits.
Finance & accounting
One export your auditor recognises
Zoho BooksCommunication
Reach families where they actually read
WhatsApp BusinessCall recordings and outcomes from a connected dialer attach to the applicant record. Conversations become part of the history, not a separate system nobody exports.
Campus hardware & identity
Devices and directories you already own
Google WorkspaceLearning & analytics
Teaching tools and your own BI stack
Moodle
Google ClassroomAPI & webhooks
If it is in the platform, it is in the API
Your website, your app, your dialer, your reporting tool and whatever your IT team builds next all read and write through documented endpoints. Nothing is locked behind an export button.
- A REST API over every core object: leads, applications, students, fees, attendance and results
- Webhooks on state change, so your systems react instead of polling
- Scoped API keys with per-endpoint permissions and rate limits
- Sandbox environment for integration work before it touches live data
- Bulk import and full export in open formats, at any time
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 }
}'Returns the lead id, the assigned counsellor and the deduplication result. A lead.stage_changed webhook fires on every subsequent movement through the funnel.
Migration
Getting your existing data in
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.
Can we run both systems in parallel for a term?
Yes, and for finance data most institutions should. A common pattern is to run admissions on Ivake for the new season while the old system serves existing students. Those students move across at the end of a term.
What if we leave?
You get a full export of every record and document, in open formats, on request. That holds after the contract ends too. We do not treat holding your data as a commercial strategy.
Book a demo
See Ivake running on your own data
Send us a sample before the call: a term of enquiries, a fee structure, or a class list. We load it and set up your programmes, 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.