aiever does not want to replace your systems
It wants to be fed by them. Keep billing where it is, keep your SMS vendor, keep your email provider — aiever sits on top and makes the data do something.
Billing, POS & commerce
The source of truth for who bought what. Push bills in and everything downstream starts working.
Tally
Bill push and reversal via TDL — live in production
Custom POS
One authenticated POST from your billing screen
Shopify
Orders via the order webhook
WooCommerce
Orders via the order webhook
In-house ERP
Plain HTTP and JSON — any language
Purchase-order apps
Stock-arrival webhook for new-lot alerts
Messaging channels
Every channel is behind an abstraction, so switching providers is configuration rather than a rebuild.
WhatsApp Business API
Official Meta platform via embedded signup
Interakt
Alternative WhatsApp provider
Twilio
Alternative WhatsApp provider
Qikberry SMS
DLT sender IDs and template IDs
Any DLT SMS gateway
Provider-agnostic SMS layer
Mailgun / SMTP
Your own email infrastructure
Social & reviews
Listen, publish and reply across the platforms your customers are already talking on.
Comments, DMs and publishing
Facebook Pages
Comments, DMs and publishing
X (Twitter)
Mentions and replies
YouTube
Comments and video upload
Google Business Profile
Review requests and review inbox
The other direction
Your systems can read from aiever too
Integration is not one-way. Your billing counter can ask aiever questions in real time.
/api/v1/customers/{mobile}/loyaltyLive points balance and tier for the customer standing at your counter.
/api/v1/vouchers/validate/{code}Accept or reject a voucher code, with the reason, before the discount is applied.
/api/v1/dashboard/summaryHeadline marketing numbers for your own dashboard or workspace widget.
All API routes are versioned under /api/v1 and authenticated per integration source.
Integration questions
Our POS is custom software. Can it connect?
Almost certainly. The integration is one authenticated HTTP POST with a JSON body. Any developer who can add an API call to your billing screen can complete it in a day, and we help with the first one.
Do you have a Tally connector?
Yes. Bills are pushed from Tally to the aiever webhook through a TDL extension, including reversals for cancelled bills. This is running in production for retailers today.
Can we keep our current SMS vendor?
In most cases yes. The SMS layer is provider-agnostic, so your existing DLT-registered sender IDs and rates carry over as a configuration change.
What if we do not have any system to connect?
You can still run aiever standalone — import your customer list from a spreadsheet and work from there. Connecting billing later only makes it better.
Send us one sample bill
Give us the JSON your billing system can produce and we will tell you on the call whether it connects as-is or needs a field added.
Or call +91 97904 03333 — Monday to Saturday, 9:00 to 18:30 IST