ResponseTap API
A REST API exposes number provisioning, call records, and reporting, capped at 1,000 requests per hour per key. Access is provisioned via the customer account. Since the Infinity acquisition the full reference sits behind login and new development targets the Infinity API.
Frequently asked questions
ResponseTap scores C on the API Report Card. A REST API exposes number provisioning, call records, and reporting, capped at 1,000 requests per hour per key. Access is provisioned via the customer account. Since the Infinity acquisition the full reference sits behind login and new development targets the Infinity API.
ResponseTap has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
ResponseTap is an intelligent call-tracking and inbound-attribution platform that connects every inbound phone call back to the marketing campaign, channel, keyword, ad, landing page, and individual web session that produced it.
Vertical: Marketing technology / Call Tracking & Inbound Attribution (cross-industry, UK/EU-led). Target market is UK, EU and (to a lesser extent) US mid-market and enterprise B2C marketers whose customers still convert by phone. Marketers and agencies deploy the ResponseTap JavaScript snippet across their websites and landing pages so every visitor receives a unique tracking phone number (visitor-level DNI).
ResponseTap is a well-established UK/EU call-tracking brand (founded 2008, headquartered in Manchester) with thousands of customers and a strong agency-channel footprint in Britain, but it is materially smaller than US category leaders CallRail (200K+ businesses) and Invoca (2,000+ enterprise customers including Fortune 500).
Yes, for any ResponseTap customer, the platform is the system of record for inbound voice activity and the closed-loop revenue truth that decides how paid-media spend is allocated.
Founded in 2008 in Manchester, UK by Ross Fobian and Richard Hamnett with the goal of bringing online-style attribution to offline phone calls.
Hard 1,000 requests/hour cap per API key is tight for high-volume agencies and warehouse-sync use cases, forcing request batching, polling backoff, and key sharding. Public API documentation has been moved from responsetap.com/api/ behind the Infinity campus portal at campus.infinity.co, which is not openly indexable and requires customer login for the full reference. Full sourced list under Sources below.
Common alternatives include Infinity Call Tracking (parent), CallRail, Invoca, CallTrackingMetrics, Marchex, Mediahawk. 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.