Call Log API Reference With Filters and JSON From RMDialer

One request, no body. Copy BASE_URL and TOKEN from Setup, then Outbound API in the RMDialer Web CRM.

GET {BASE_URL}/api/datalake/outbound/call-logs
Authorization: Bearer {TOKEN}
Accept: application/json

The token can also ride in the URL as ?token= when a tool cannot set headers, such as a spreadsheet import. A header is safer, because URLs end up in logs.

Call log API example request (curl)

curl -G "$BASE_URL/api/datalake/outbound/call-logs" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "from=2026-09-01" \
  --data-urlencode "to=2026-09-30" \
  --data-urlencode "type=outgoing" \
  --data-urlencode "per_page=500"

Python: every missed call this month

import time
import requests

def fetch_call_logs(base_url, token, **filters):
    """Yield every call that matches the filters, one page of 500 at a time."""
    page = 1
    while True:
        r = requests.get(
            f"{base_url}/api/datalake/outbound/call-logs",
            headers={"Authorization": f"Bearer {token}", "Accept": "application/json"},
            params={**filters, "page": page, "per_page": 500},
            timeout=30,
        )
        if r.status_code == 429:      # over 60 requests a minute: wait, then retry this page
            time.sleep(5)
            continue
        r.raise_for_status()
        body = r.json()
        yield from body["data"]
        if not body["meta"]["has_more"]:
            break
        page += 1

for call in fetch_call_logs(BASE_URL, TOKEN, type="missed", **{"from": "2026-10-01"}):
    print(call["call_at"], call["phone_number"], call["called_by"]["name"])

Node: incremental sync with updated_since

// Node 18+ (built-in fetch). Pulls only what changed since the last run.
async function* fetchCallLogs(baseUrl, token, filters = {}) {
  for (let page = 1; ; page++) {
    const qs = new URLSearchParams({ ...filters, page, per_page: 500 });
    const res = await fetch(`${baseUrl}/api/datalake/outbound/call-logs?${qs}`, {
      headers: { Authorization: `Bearer ${token}`, Accept: 'application/json' },
    });
    if (res.status === 429) { await new Promise((r) => setTimeout(r, 5000)); page--; continue; }
    if (!res.ok) throw new Error(`Call log API ${res.status}`);
    const body = await res.json();
    yield* body.data;
    if (!body.meta.has_more) return;
  }
}

// Save when this run started, written in the account time zone (meta.timezone), for the next run.
const startedAt = startOfRunInAccountZone();
for await (const call of fetchCallLogs(BASE_URL, TOKEN, { updated_since: lastSyncStartedAt })) {
  await upsertCall(call.id, call); // the id is stable, so a re-read call updates instead of duplicating
}

The complete scripts, including that time-zone helper and PHP and curl versions, are in rmdialer/api-examples on GitHub.

Errors and the rate limit

• 401: the token is missing or wrong.
• 403: the token has been turned off in Setup, Outbound API.
• 422: a parameter is invalid, for example type=answered or per_page=1000.
• 429: more than 60 requests in a minute. Wait and repeat the same page.

Android has its own call log API, CallLog.Calls, and it is a different thing. It reads the log of the one phone your app is installed on, needs the READ_CALL_LOG permission, and Google Play only allows that permission for the default phone app and a short list of exceptions. It knows numbers and durations, not leads or employees.

RMDialer's call log API is the other half of the job: RMDialer is the dialer on each phone, so it reads CallLog.Calls there, attaches the lead and the caller, and your server reads every phone at once over HTTPS. If you are building the Android side yourself, start with how to read call logs in Android programmatically and the READ_CALL_LOG Google Play policy.