Ranobes APIranobes.top ↗
Access novel chapter listings, full chapter text, and book metadata from ranobes.top via 3 structured endpoints. Covers titles, genres, ratings, and more.
What is the Ranobes API?
The ranobes.top API exposes 3 endpoints for retrieving web novel data: chapter listings with pagination, full chapter text content, and detailed book metadata. Using list_chapters, you can page through a novel's complete chapter history; get_chapter_content returns the full text of any individual chapter; and get_book_info surfaces author, genres, tags, rating, status, and view count for any book by its numeric ID.
curl -X GET 'https://api.parse.bot/scraper/74ef149f-8adf-4285-9aa9-55ba2645bcae/list_chapters?page=1&book_id=1205249' \ -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 ranobes-top-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: Ranobes_API SDK — bounded, re-runnable; every call capped."""
from parse_apis.Ranobes_API import Ranobes, ChapterNotFound
client = Ranobes()
# Fetch book metadata by ID.
book = client.books.get(book_id="1205249")
print(book.title, book.author, book.status, book.rating)
# Browse chapters for the novel, auto-iterated across pages.
for chapter in book.chapters(limit=3):
print(chapter.title, chapter.date)
# Drill-down: get full text content of the first chapter.
first = book.chapters(limit=1).first()
if first:
detail = first.content()
print(detail.title, detail.novel_title, len(detail.content), "chars")
# Typed error handling on a direct chapter lookup.
try:
full = client.chapter_contents.get(chapter_id="3226204")
print(full.title, full.novel_title)
except ChapterNotFound as e:
print("gone:", e.chapter_id)
print("exercised: books.get / book.chapters / chapter.content / chapter_contents.get")
List chapters for a novel, ordered newest-first. Returns 25 chapters per page with metadata including title, date, and direct link. Results are auto-iterated across pages.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for chapter listing (1-based). |
| book_idrequired | string | Numeric book/novel identifier (e.g. 1205249 for Shadow Slave). |
{
"type": "object",
"fields": {
"page": "integer — current page number",
"book_id": "integer — numeric book identifier",
"chapters": "array of chapter objects with id, title, date, link",
"book_title": "string — name of the novel",
"total_pages": "integer — total number of pages",
"total_chapters": "integer — total chapter count"
},
"sample": {
"data": {
"page": 1,
"book_id": 1205249,
"chapters": [
{
"id": "3226204",
"date": "2026-07-22 04:06:57",
"link": "https://ranobes.top/shadow-slave-v741610-1205249/3226204.html",
"title": "Chapter 3114: Missing Core"
}
],
"book_title": "Shadow Slave",
"total_pages": 125,
"total_chapters": 3114
},
"status": "success"
}
}About the Ranobes API
Chapter Listings
The list_chapters endpoint accepts a required book_id (the numeric identifier found in ranobes.top novel URLs) and an optional page integer. It returns up to 25 chapters per page, ordered newest-first. Each chapter object in the chapters array includes id, title, date, and link. The response also carries book_title, total_pages, and total_chapters, so you can determine upfront how many pages to iterate across a novel's full history.
Chapter Content
get_chapter_content takes a required chapter_id (obtained from list_chapters results) and an optional book_id. It returns the title, the full content string, the chapter_id, and the novel_title. This is the primary endpoint for reading or indexing the actual prose of any chapter.
Book Metadata
get_book_info returns a complete snapshot of a novel's metadata given its book_id. Response fields include title, author, cover_image URL, genres array, tags array, status (e.g. Ongoing or Completed), rating out of 5, views, and a link back to the novel page. This endpoint is useful for building catalog indexes or filtering novels by genre, tag, or publication status without fetching chapter content.
The Ranobes API is a managed, monitored endpoint for ranobes.top — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ranobes.top 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 ranobes.top 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 personal reading tracker that monitors new chapters using
list_chaptersand thedatefield. - Index full chapter text from
get_chapter_contentfor offline reading or search across a novel. - Aggregate novel metadata via
get_book_infoto compare ratings and view counts across titles. - Filter novels by genre or tag using the
genresandtagsarrays fromget_book_info. - Track publication status changes (Ongoing vs Completed) across a watchlist of book IDs.
- Generate a chapter count summary for a novel using
total_chaptersfromlist_chapters. - Populate a recommendation engine with cover images, author names, and descriptions from
get_book_info.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does ranobes.top have an official developer API?+
What does `list_chapters` return and how does pagination work?+
list_chapters returns 25 chapter objects per page, ordered newest-first. Each object includes the chapter id, title, date, and link. The response includes total_pages and total_chapters so you can calculate how many requests are needed to retrieve a novel's complete chapter list. Pass the page parameter (1-based) to step through pages.Does `get_book_info` return a synopsis or description field?+
get_book_info include title, author, cover_image, genres, tags, status, rating, views, book_id, and link. A full prose description field is not listed in the current spec. You can fork this API on Parse and revise it to add a description field if that data appears on the novel page.Is there an endpoint to search for novels by title or genre?+
book_id. You can fork this API on Parse and revise it to add a search endpoint that accepts a title or genre query.How fresh is the chapter listing data, and will very recently published chapters appear immediately?+
list_chapters reflects the chapter list as it exists on ranobes.top at the time of the request, ordered newest-first. There is no caching delay documented in the spec, but ranobes.top itself may have a lag between a translator posting a chapter and it appearing in listings. If a chapter is missing, retry after a short interval.