INKR APIcomics.inkr.com ↗
Search INKR Comics titles, fetch manga details with chapter lists, chapter metadata, and page-level viewer data via 4 structured JSON endpoints.
What is the INKR API?
The INKR Comics API exposes 4 endpoints covering title search, full manga details, chapter metadata, and reader page lists from comics.inkr.com. The search_titles endpoint returns up to 50 titles per query with relevance scores, genre arrays, creator roles, and cover URLs. get_manga delivers a complete chapter list alongside reading direction, monetization type, and summary text. Together these endpoints give structured access to INKR's catalog of manga, manhua, and webtoons.
curl -X GET 'https://api.parse.bot/scraper/87420965-3ab5-4945-8892-554612fadb9c/search_titles?query=faust' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search of INKR Comics titles (manga, manhua, webtoons). Returns up to `limit` titles ordered by the site's relevance score (highest first), each with creators, genre names, release status, and cover image URL. One search call plus two hydration calls per request. A query with no matching titles returns an empty results array. Not paginated; the site returns only the top matches.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of titles to return; values above 50 are clamped to 50. The site may return fewer than requested. |
| queryrequired | string | Free-text search term matched against title names, keywords and creators. |
{
"type": "object",
"fields": {
"query": "the search term echoed back",
"total": "number of results returned",
"results": "array of matching titles, ordered by descending relevance score",
"results[].score": "site relevance score (number, higher is better)",
"results[].genres": "array of genre name strings",
"results[].creators": "array of {creator_id, name, role} where role is story, art or publisher",
"results[].title_id": "numeric string title identifier; pass to get_manga.title_id",
"results[].cover_url": "cover image URL",
"results[].release_status": "e.g. completed or ongoing"
},
"sample": {
"data": {
"query": "faust",
"total": 1,
"results": [
{
"name": "Frau Faust",
"score": 176.53262,
"genres": [
"Supernatural",
"Adventure",
"Fantasy"
],
"creators": [
{
"name": "Kore Yamazaki",
"role": "art",
"creator_id": "2086"
},
{
"name": "Kodansha",
"role": "publisher",
"creator_id": "405"
}
],
"title_id": "2086",
"cover_url": "https://i1.inkr.com/p/image/a8ae80107d0be245f8398a837592f647.png/900.jpg",
"style_origin": "manga",
"release_status": "completed",
"total_published_chapters": 21
}
]
},
"status": "success"
}
}About the INKR API
Title Search and Discovery
The search_titles endpoint accepts a query string matched against title names, keywords, and creators. Results are ordered by descending relevance score and include genres (an array of genre name strings), creators (each with creator_id, name, and role — one of story, art, or publisher), cover_url, release_status (e.g. completed or ongoing), and a title_id to pass downstream. The limit parameter accepts integers up to 50; values above that are clamped.
Title Details and Chapter Lists
get_manga takes a title_id and returns the full title record: summary, reading_direction (rtl or ltr), reading_style, monetization_type, like_count, page_read_count, and a genres array where each entry carries genre_id, name, and type (main, theme, or demographic). The chapters array is in reading order and includes per-chapter revenue_type, is_free flag, coin_price, and page count — enough to identify which chapters are freely accessible before fetching further detail.
Chapter Metadata and Access Signals
get_chapter returns metadata for a single chapter by chapter_id: order within the title, total_pages, coin_price, revenue_type, publish and update dates, and has_full_pages — a boolean that tells you whether get_viewer will return every page or only a preview. This lets you gate viewer calls to free chapters and avoid unnecessary requests on paywalled content.
Viewer / Reader Page Data
get_viewer returns the ordered pages array for a chapter, each entry containing index, width, and height in pixels. The access field is full when every page is returned or preview for paywalled chapters. total_pages reflects the true chapter length even when pages is truncated. The response also includes next_chapter_id and title_id for navigation without a separate lookup.
The INKR API is a managed, monitored endpoint for comics.inkr.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when comics.inkr.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 comics.inkr.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?+
- Build a manga catalog browser using
search_titlesgenre arrays and cover URLs to display filtered title grids. - Track release status changes (completed vs ongoing) across a watchlist of title IDs via
get_manga. - Identify freely accessible chapters before fetching pages by checking
is_freein theget_mangachapters array. - Construct a reading progress tracker using
orderandtotal_pagesfromget_chapterresponses. - Resolve reading direction (
rtlorltr) per title fromget_mangato drive a custom reader UI layout. - Aggregate creator catalogs by filtering
get_mangaresults on a specificcreator_idacross multiple titles. - Render preview images for paywalled chapters using the partial
pagesarray fromget_viewerwhereaccessispreview.
| 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 INKR Comics have an official developer API?+
What does `get_viewer` return for subscription-only chapters?+
get_viewer returns access: preview and a partial pages array. total_pages still reflects the full chapter length so you know how much content exists, but only the publicly available preview pages are included in pages.Are user reviews, ratings, or reading lists exposed by these endpoints?+
like_count, page_read_count), chapter lists, and reader page data. User-generated reviews and personal reading lists are not exposed. You can fork this API on Parse and revise it to add endpoints targeting those data surfaces.Does the API support paginating through the full INKR catalog, not just search results?+
search_titles, which returns up to 50 results per query. Browsing or paginating the full catalog is not available as a dedicated endpoint. You can fork this API on Parse and revise it to add a catalog-browse endpoint.How do I know if a chapter requires payment before calling `get_viewer`?+
has_full_pages in the get_chapter response. When it is false, only preview pages will be returned by get_viewer. You can also inspect is_free and revenue_type in the chapters array returned by get_manga to filter before making individual chapter calls.