Truecaller APIdeveloper.truecaller.com ↗
Access Truecaller Developer Portal blog posts and SDK documentation via 3 endpoints. Retrieve articles, content blocks, and the full 214-page doc structure.
What is the Truecaller API?
This API provides access to the Truecaller Developer Portal through 3 endpoints, covering developer blog articles and the complete SDK documentation site structure. Use list_blog_posts to retrieve paginated post summaries filtered by category, get_blog_post to fetch full structured content for any article, and get_documentation_pages to traverse all 214 documentation pages across Android, iOS, Mobile Websites, and MID Verification SDK topics.
curl -X GET 'https://api.parse.bot/scraper/14fb83c8-3576-4143-b21e-6ad1ae6b0434/list_blog_posts?category=product' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace developer-truecaller-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Truecaller Developer Portal SDK — bounded, re-runnable."""
from parse_apis.developer_truecaller_com_api import TruecallerDev, Category, PostNotFound
client = TruecallerDev()
# List product blog posts, capped at 5 total items.
for summary in client.post_summaries.list(category=Category.PRODUCT, limit=5):
print(summary.title, summary.first_publication_date)
# Drill into the first post's full content via the summary→detail navigation.
first_summary = client.post_summaries.list(limit=1).first()
if first_summary is not None:
post = first_summary.details()
print(post.title, post.author_uid)
for block in post.content[:3]:
print(f" [{block.type}] {block.text[:80]}")
# Point lookup by uid discovered from the listing above.
if first_summary is not None:
try:
detail = client.posts.get(uid=first_summary.uid)
print(detail.title, detail.category_uid)
except PostNotFound:
print("Post was removed or uid is invalid")
# Retrieve the full documentation site structure.
docs = client.documentations.get()
print(f"Documentation: {docs.total_pages} pages")
for page in docs.pages[:3]:
print(f" {page.title} -> {page.pathname}")
print("exercised: post_summaries.list / details / posts.get / documentations.get")
List developer blog posts from the Truecaller Developer Portal, ordered by publication date (newest first). Supports filtering by category. Returns paginated results with up to 20 posts per page.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
| category | string | Filter posts by category slug. Omitting returns all categories. |
{
"type": "object",
"fields": {
"page": "current page number",
"posts": "array of blog post summaries with uid, title, category, featured_image_url, and publication dates",
"total_pages": "total number of pages",
"total_results": "total number of matching posts",
"results_per_page": "number of results per page (20)"
},
"sample": {
"data": {
"page": 1,
"posts": [
{
"uid": "sim-device-binding",
"title": "Enhancing Security and Compliance: Introducing SIM & Device Binding for Truecaller SDK",
"category": "Product",
"category_uid": "product-blog",
"featured_image_url": "https://images.prismic.io/tc4d/ajj1clbRV8_Qftzk_20260617_Simupgradecoverimage.png?auto=format,compress",
"last_publication_date": "2026-07-02T09:42:25+0000",
"first_publication_date": "2026-07-02T09:34:35+0000"
}
],
"total_pages": 1,
"total_results": 4,
"results_per_page": 20
},
"status": "success"
}
}About the Truecaller API
Blog Post Endpoints
list_blog_posts returns up to 20 post summaries per page, each including a uid (slug), title, category, featured_image_url, and both publication and modification timestamps. You can pass a category slug to filter results — for example, limiting results to "best-practices" or "success-story" entries — and use the page parameter together with total_pages to iterate through all matching posts.
Full Article Content
get_blog_post accepts a uid from the listing endpoint and returns the complete article. The content field is an array of structured blocks — each with a type (paragraph, heading, image, HTML embed) and associated text or url — allowing you to render or parse the article without stripping markup. The response also includes author_uid, category_uid, first_publication_date, and last_publication_date in ISO 8601 format.
Documentation Structure
get_documentation_pages requires no parameters and returns all 214 documentation pages in a single response. Each entry includes an id, title, pathname (URL path within the doc site), description, and a breadcrumbs array that encodes the page's position in the hierarchy. Coverage spans Android SDK, iOS SDK, Mobile Websites, and MID Verification SDK sections, making it straightforward to build a navigable index or check which topics exist before fetching external content.
The Truecaller API is a managed, monitored endpoint for developer.truecaller.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when developer.truecaller.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official developer.truecaller.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Mirror the Truecaller Developer Portal blog into an internal knowledge base, preserving category and publication date metadata
- Build a changelog tracker that monitors
last_publication_dateon blog posts for SDK update announcements - Extract structured content blocks from SDK integration guides to feed into a developer-facing search index
- Generate a sitemap or navigation tree of Truecaller SDK docs using the
pathnameandbreadcrumbsfields fromget_documentation_pages - Filter blog posts by category slug (e.g. 'best-practices') to surface relevant articles in a developer onboarding flow
- Inventory all 214 documentation pages to identify coverage gaps across Android, iOS, and Mobile Websites SDK topics
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Truecaller have an official developer API for this content?+
What does `get_blog_post` return beyond basic metadata?+
content array of typed blocks — paragraphs, headings, images, and HTML embeds — each with type and associated text or url fields. This means the full article body is available in a structured, block-by-block format rather than as raw HTML.Does `list_blog_posts` expose the full article body?+
list_blog_posts returns summaries only: uid, title, category, featured_image_url, and publication dates. To get the full structured content, pass the uid to get_blog_post.Does the API expose individual documentation page content, not just the page structure?+
get_documentation_pages returns metadata for all 214 pages — title, pathname, description, and breadcrumbs — but does not fetch the body content of each documentation page. You can fork this API on Parse and revise it to add an endpoint that retrieves the full content of a specific documentation page by its pathname.Can I retrieve author profile details like name, bio, or avatar?+
author_uid slug but no further author metadata such as display name, bio, or profile image. You can fork this API on Parse and revise it to add a dedicated author endpoint that resolves those details.