Fliptru APIfliptru.com.br ↗
Access comic metadata, engagement stats, rankings, and search from Fliptru, Brazil's webcomic platform. 9 endpoints covering titles, authors, views, and more.
What is the Fliptru API?
The Fliptru API exposes 9 endpoints covering comic metadata, engagement statistics, ranked listings, and search across Fliptru's Brazilian webcomic catalog. The get_comic endpoint returns 10 fields per title — including view counts, like counts, chapter totals, author username, category, and age rating — identified by URL slug. Listing endpoints cover most-popular, best-seller, promoted, series, completed series, one-shots, and webtoons, each returning paginated card objects.
curl -X GET 'https://api.parse.bot/scraper/9d8b4d73-182b-4025-a47f-b91a4d30be83/get_comic?slug=sense-life' \ -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 fliptru-com-br-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: Fliptru Comics API — browse listings, search, and fetch comic details."""
from parse_apis.fliptru_com_br_api import Fliptru, ComicNotFound
client = Fliptru()
# Browse the best-seller ranking, capped at 5 items.
for listing in client.listings.best_sellers(limit=5):
print(listing.title, "|", listing.category, "|", listing.age_rating)
# Search for a comic by name, then fetch its full detail.
hit = client.search_hits.search(query="sense", limit=1).first()
if hit is not None:
# The search hit URL ends with the slug we need.
slug = hit.url.rstrip("/").rsplit("/", 1)[-1]
try:
comic = client.comics.get(slug=slug)
except ComicNotFound:
print("Comic not found for slug:", slug)
else:
print(comic.title, "by", comic.author)
print("Chapters:", comic.chapters, "| Views:", comic.views, "| Likes:", comic.likes)
# List a few promoted comics.
for listing in client.listings.promoted(limit=3):
print(listing.title, listing.type, listing.url)
print("exercised: listings.best_sellers / search_hits.search / comics.get / listings.promoted")
Retrieve detailed information for a single comic on Fliptru by its URL slug. Returns the comic's thumbnail image URL, category, title, author, chapter count, view count, likes, comments, saves, shares, and age rating. One upstream request per call; no pagination.
| Param | Type | Description |
|---|---|---|
| slugrequired | string | URL slug of the comic (the path segment after /comic/, e.g. 'sense-life', 'lampiao'). |
{
"type": "object",
"fields": {
"autor": "Author username",
"likes": "Like count as displayed (e.g. '99.3K')",
"salvos": "Save/bookmark count as displayed (e.g. '11.4K')",
"titulo": "Comic title",
"capitulos": "Total number of published chapters (integer)",
"categoria": "Comic category/genre (e.g. Ação, Romance)",
"thumbnail": "URL of the comic's banner/cover image",
"comentarios": "Comment count as displayed (e.g. '4.62K')",
"visualizacoes": "View count as displayed on the site (e.g. '4.45M', '471K')",
"compartilhamentos": "Share count as displayed (e.g. '3.49K')",
"classificacao_etaria": "Age rating badge text (e.g. 'A16', 'L')"
},
"sample": {
"data": {
"autor": "Glitch_Tellend",
"likes": "99.3K",
"salvos": "11.4K",
"titulo": "Sense Life",
"capitulos": 17,
"categoria": "Ação",
"thumbnail": "https://media.fliptru.com.br/media/comic/sense-life/bannerred.png",
"comentarios": "4.62K",
"visualizacoes": "4.45M",
"compartilhamentos": "3.49K",
"classificacao_etaria": "A16"
},
"status": "success"
}
}About the Fliptru API
Comic Detail and Engagement Data
The get_comic endpoint accepts a slug parameter (the path segment after /comic/, e.g. sense-life or lampiao) and returns a single comic's full metadata. Response fields include titulo, autor, categoria, capitulos (integer chapter count), thumbnail (cover image URL), classificacao_etaria (age rating), and four engagement counters — visualizacoes, likes, salvos, and compartilhamentos — all formatted as display strings such as 4.45M or 99.3K. The comentarios field gives the comment count in the same format.
Ranking and Listing Endpoints
Two ranking endpoints — get_most_popular_list and get_best_seller_list — return the full contents of Fliptru's respective ranking pages, including promoted and ad-slot entries. Each item in the items array carries url, position (integer rank where numbered), thumbnail, type, category, title, and classificacao_etaria. Neither endpoint accepts pagination parameters; they return everything on the page in a single call.
Four format-specific listing endpoints — get_series_list, get_completed_series_list, get_one_shot_list, and get_webtoons_list — plus get_promoted_list all accept an optional page integer parameter. Each page returns up to 12 items. When page is omitted, the default first page is returned. The position field is null on these listings since they are not ranked.
Search
The search_comics endpoint accepts a required query string (e.g. sense, naruto) and returns a deduplicated list of matching comics. Each result includes name, author, and url. Results whose URL contains /category/ are filtered out automatically, so only individual comic entries are returned. The endpoint makes one request and does not support pagination.
The Fliptru API is a managed, monitored endpoint for fliptru.com.br — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fliptru.com.br 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 fliptru.com.br 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?+
- Track engagement growth for a specific comic by polling
visualizacoes,likes, andsalvosover time usingget_comic. - Build a Brazilian webcomic discovery feed by pulling paginated results from
get_series_listandget_webtoons_list. - Identify trending titles by comparing position and engagement data across
get_most_popular_listandget_best_seller_list. - Filter content by age rating using the
classificacao_etariafield returned on every listing and detail endpoint. - Resolve a comic slug from a user search query using
search_comicsbefore fetching full details withget_comic. - Aggregate completed series for a recommendation engine using
get_completed_series_listwith thepageparameter. - Audit author output by searching an author's name via
search_comicsand cross-referencingcapituloscounts fromget_comic.
| 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 Fliptru offer an official developer API?+
What does `get_comic` return that the listing endpoints don't?+
get_comic is the only endpoint that returns engagement counters: visualizacoes, likes, salvos, compartilhamentos, and comentarios. It also returns capitulos (chapter count) and autor. Listing endpoints return card-level data only — url, position, thumbnail, type, category, title, and classificacao_etaria — with no engagement figures.Do the ranking endpoints include paid promotional slots?+
get_most_popular_list and get_best_seller_list return every item on the page, including promoted and ad-slot entries. Your code should account for these when interpreting position values or filtering results.Can I retrieve the actual chapter pages or panel images for a comic?+
Is there a way to filter listing results by category or age rating directly in the API?+
categoria and classificacao_etaria fields are included in each item, so filtering must be applied client-side. You can fork this API on Parse and revise it to add server-side filtering if your use case requires it.