Truecaller
Truecaller is the Stockholm-based caller identification and spam-blocking platform (atomico and balderton-capital portfolio) used by hundreds of millions of people to know who is calling. For developers it publishes the Truecaller SDK for Android, iOS, mobile web, Flutter, React Native and Shopify - one-tap phone-number verification built on OAuth 2.0 with PKCE (authorization code + refresh token, OIDC-style userinfo) plus a drop-call / IM-OTP flow for non-Truecaller users. Truecaller for Business adds REST APIs on enterprise-portal-noneu.truecaller.com for verified business caller ID: call personalisation (dynamic caller ID), number management, verified campaigns, and Call Me Back / User Feedback webhooks.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Truecaller the way a machine reads it — 9 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Truecaller scores 40.4/100 (thin), with a separate agent-readiness read of 30/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Truecaller
Each block below is one kind of artifact we hold for Truecaller. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Truecaller OAuth User Verification API
The backend half of the Truecaller OAuth SDK flow. After the mobile SDK returns an authorization code, partners exchange it at POST /v1/token (authorization_code grant with PKCE...
Truecaller Non-Truecaller User Verification API
Server-side validation for the drop-call / IM-OTP verification flow that covers users without the Truecaller app. GET /v1/otp/client/installation/phoneNumberDetail/{accessToken}...
Truecaller Web SDK Profile API
Profile retrieval for the mobile-web (deep link) verification flow. After a user consents in the Truecaller app, Truecaller POSTs the accessToken and requestId to the partner's ...
Truecaller for Business API
REST APIs for Truecaller's Verified Business Caller ID platform. Partners exchange a Key ID + Secret API Key for a 60-minute bearer token (POST /clients/{clientAccountId}/token)...
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Truecaller Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Truecaller — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/truecaller · machine-readable index on apis.io