CallTrackingMetrics API
CallTrackingMetrics publishes a documented REST API with webhooks and SDKs for PHP, Ruby, Python, and Node. Keys are self-serve for paying customers over HTTP Basic auth, with no OAuth. Rate limits are undocumented and bulk history export runs through Professional Services.
Frequently asked questions
CallTrackingMetrics scores D+ on the API Report Card. CallTrackingMetrics publishes a documented REST API with webhooks and SDKs for PHP, Ruby, Python, and Node. Keys are self-serve for paying customers over HTTP Basic auth, with no OAuth. Rate limits are undocumented and bulk history export runs through Professional Services.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
CallTrackingMetrics (CTM) is a call tracking, conversation intelligence, and contact-center automation platform that connects every inbound call, text, chat, and form to the marketing campaign, ad, or keyword that produced it.
Vertical: Marketing technology / Call Tracking & Conversation Analytics (cross-industry). Marketers and agencies put unique tracking numbers on landing pages, Google/Meta ads, GMB listings, and email so every inbound call is attributed to the campaign, keyword, ad creative, and visitor session that drove it.
CTM is one of the top three SMB/mid-market call-tracking platforms (alongside CallRail and WhatConverts) and the recognized leader for agencies that need a deeper feature set than CallRail.
Yes, for any CTM customer, the platform is the system of record for inbound voice, SMS, web form, and chat activity and the closed-loop revenue truth that decides how paid-media spend gets allocated.
Founded 2009 in Severna Park, Maryland by Todd Fisher and Laure Fisher (husband-and-wife co-founders); Todd previously co-founded SimoSoftware (sold to RevolutionHealth in 2005).
Published rate-limit policy is not documented in the public API guide; customers report having to discover throttling behavior empirically. API authentication is HTTP Basic with long-lived Access/Secret key pairs, no OAuth flow or short-lived token support, which complicates third-party integrations and key rotation. Full sourced list under Sources below.
Common alternatives include CallRail, Invoca, WhatConverts, Marchex, Ringba, Nimbata. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.