Your CRM cannot see a mobile call it was never part of. With RMDialer, the dialer API for CRM products, every call your users make arrives as an event.

A REST API over HTTPS with token auth, plus optional webhooks. Nothing exotic: JSON in, JSON out, a bearer token in the header. Tell us the use case and we will send docs and sandbox credentials so you can see real payload shapes before you write anything against it.

You can, and for a single-user utility that is the right answer: android.provider.CallLog is documented by Google and needs no vendor. It stops being the right answer for a business product, because you then own a Play Store review process for a sensitive permission group, the OEM battery-management problem that silently kills background sync on many Indian handsets, and per-device reconciliation for calls that happened offline. Our developer page covers the call-log data model in detail if you want to compare properly.

Two supported shapes: subscribe a webhook and receive each call as it is reported, or poll a cursor endpoint and page through everything since your last position. Webhooks suit live pipeline updates, the cursor suits nightly reconciliation. Most integrations end up using both, webhooks for immediacy and a nightly cursor sweep as the safety net.

Yes, and this matters more than it sounds. A caller who dials from their contacts out of habit still produces a call event, because the handset's own call log is the source. What those calls lack is the structured outcome, since nobody was prompted for one, and that absence is itself a signal worth surfacing in your product.

They queue on the device and deliver when the connection returns, which can be hours later. This is the single most common integration bug we see: a consumer keyed on arrival time drops the afternoon a caller spent in a basement. Key on the event id, treat delivery as at-least-once, and page on the cursor rather than on a timestamp.

Yes, and with an owner attached, so the lead lands in one specific caller's queue rather than a shared pile. The app can also poll your own endpoint directly as a lead source, which some teams prefer because it keeps your CRM the system of record and avoids you maintaining an outbound integration at all.

Yes, with seeded data, so you can build against realistic payloads before any real handset is involved. Ask for access with a sentence about what you are building; the sandbox has its own credentials and cannot touch production accounts.

Generous enough that normal integrations never meet them, and documented in the pack you get with your key rather than quoted here where they would go stale. If you are planning a bulk historical backfill, tell us first and we will size it with you rather than have you discover a limit at three in the morning.

HTTPS throughout, bearer tokens that you can rotate, and scoping so a key reaches only the accounts it should. What crosses the wire is call metadata and the text your users typed.

You do, inside your own product. Your users experience your CRM with a working phone layer, and the dialer can carry your brand entirely if you take the whitelabel route, which several partners have: apps running on this same backend already ship under different names on Play.

No. Every brand on the platform talks to the same endpoints against the same backend, so an integration built once works across all of them. That is deliberate: a partner who later moves to their own branded app does not rewrite anything.

The API is included rather than sold as a tier: your users pay the normal ₹159 per user per month for the app and the integration comes with it. There is no per-call or per-event charge, because the calls run on your users' own SIMs and we are not carrying any voice traffic to meter.

Yes, through the same cursor endpoint by starting from the beginning rather than from your last position. Worth doing once at go-live so a customer switching to your product does not see an empty history where their last six months of calls should be.

Live call audio and anything requiring the voice path, because on SIM calls the voice never passes through us. Recordings exist only where the handset's own dialer captured them and the user attached them. If your product needs guaranteed audio on every call, a cloud telephony vendor is the correct integration and we will say so rather than sell around it.

Use the form on this page with a couple of lines about the product and the direction data needs to flow. You get docs, sandbox credentials and an engineer to talk to, and the sample requests on the developers page are enough to make a first call within an hour of receiving a key.