Discover/Shueisha API
live

Shueisha APImangaplus.shueisha.co.jp

Access MANGA Plus manga catalog, chapter pages, rankings, and featured lists via 6 structured endpoints. Filter by language, status, publisher label, and more.

Endpoint health
verified 3h ago
get_manga
get_chapter
list_manga
get_updates
get_featured
6/6 passing latest checkself-healing
Endpoints
6
Updated
4h ago

What is the Shueisha API?

The MANGA Plus API exposes 6 endpoints covering the full public catalog of Shueisha's MANGA Plus platform — including titles, chapter pages, rankings, and curated featured lists. The get_chapter endpoint returns an ordered page array with image URLs, dimensions, and per-page encryption keys needed to render each page. The list_manga endpoint returns every title across Ongoing, Completed, and One-shot tabs in a single call, with language and publisher label filters.

This call costs1 credit / call— charged only on success
Try it
Keep only works carrying this publisher label. Use CREATORS for MANGA Plus Creators (award / user-submitted) titles, which appear in the one_shot list. Omitted = all labels.
Which manga list tab to return.
Keep only works that have an edition in this language and return only that edition. Omitted = all languages.
api.parse.bot/scraper/4e0ad316-f616-48bb-9e23-ef7b48c36479/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/4e0ad316-f616-48bb-9e23-ef7b48c36479/list_manga?status=ongoing' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 6 totalmissing one? ·

Returns the full MANGA Plus manga list for one status tab (Ongoing, Completed or One-shot) in a single call; the site does not paginate this list. Each record is one original work grouped with all of its translated editions (one title per language, each with its own title_id usable in get_manga), plus genre tags, the publisher label (e.g. WJ = Weekly Shonen Jump, CREATORS = MANGA Plus Creators award titles) and the next chapter timestamp. The optional label filter keeps only works with that label; the optional language filter keeps only works that have an edition in that language and drops the other-language editions from each record. source_total_manga is the unfiltered count from the site, count is the number of records returned. Filters that match nothing return an empty manga array.

Input
ParamTypeDescription
labelstringKeep only works carrying this publisher label. Use CREATORS for MANGA Plus Creators (award / user-submitted) titles, which appear in the one_shot list. Omitted = all labels.
statusstringWhich manga list tab to return.
languagestringKeep only works that have an edition in this language and return only that edition. Omitted = all languages.
Response
{
  "type": "object",
  "fields": {
    "count": "integer, number of works returned after filters",
    "manga": "array of works; each has name, label (publisher label code or null), label_image, next_chapter_start_timestamp (unix seconds), tags (genre tag/slug pairs) and titles (one edition per language with title_id, name, author, portrait_image_url, language, update_status)",
    "status": "echo of the requested list tab",
    "all_tags": "array of all genre tags available on the site (tag, slug)",
    "source_total_manga": "integer, number of works in the site's unfiltered list for this tab",
    "available_languages": "array of languages with titles_count as reported by the site"
  },
  "sample": {
    "data": {
      "count": 60,
      "manga": [
        {
          "name": "No Devil",
          "tags": [
            {
              "tag": "Manga Award",
              "slug": "manga-award"
            }
          ],
          "label": "CREATORS",
          "titles": [
            {
              "name": "No Devil",
              "author": "Senchiro",
              "language": "eng",
              "title_id": 100832,
              "view_count": 0,
              "update_status": "NONE",
              "portrait_image_url": "https://jumpg-assets.tokyo-cdn.com/secure/title/100832/title_thumbnail_portrait_list/613397.jpg",
              "landscape_image_url": null
            }
          ],
          "label_image": {
            "label_id": 8,
            "image_url": "https://jumpg-assets.tokyo-cdn.com/secure/label/475403.webp"
          },
          "next_chapter_start_timestamp": 1788102000
        }
      ],
      "status": "one_shot",
      "all_tags": [
        {
          "tag": "Battle / Action",
          "slug": "battle-action"
        }
      ],
      "source_total_manga": 408,
      "available_languages": [
        {
          "language": "eng",
          "titles_count": 767
        }
      ]
    },
    "status": "success"
  }
}

About the Shueisha API

Catalog and Title Data

The list_manga endpoint returns the full manga list for one status tab (ONGOING, COMPLETED, or ONE_SHOT) in a single unpaginated response. Each record in the manga array groups all translated editions of one original work, where each edition has its own title_id usable across other endpoints. Filters include language (e.g. eng, spa) and label (e.g. CREATORS for MANGA Plus Creators content). The response also includes all_tags for genre filtering and available_languages with per-language title counts.

get_manga accepts a title_id and returns the full detail record: synopsis (overview), content rating (ALLAGE / TEEN / TEENPLUS / MATURE), update_timing, number_of_views, and chapter_groups. Chapter groups split the chapter list into first_chapters, mid_chapters, and last_chapters, each entry carrying a chapter_id, name, sub_title, and thumbnail URL for use in get_chapter.

Chapter Pages

get_chapter takes a chapter_id and an optional img_quality parameter. It returns a pages array in reading order where each entry includes image_url, width, height, page_type (SINGLE / LEFT / RIGHT / DOUBLE), and an encryption_key — a hex key required to decode each image. The last_page object indicates the next chapter ID (or null at the series end) and a next_timestamp for scheduled releases.

Updates, Featured, and Rankings

get_updates returns the home page state: update_groups bucketed by days_ago, each containing works with new chapter releases and their update_status (NEW / UP / REEDITION). get_featured returns curated title_lists organized by magazine, genre, or campaign, each title carrying title_id, author, and cover image URLs. get_ranking returns ranked manga for Hottest, Trending, or Completed tabs with rank, score, original_title_id, per-language editions, and an updated_timestamp showing when the site last refreshed the ranking.

Reliability & maintenanceVerified

The Shueisha API is a managed, monitored endpoint for mangaplus.shueisha.co.jp — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when mangaplus.shueisha.co.jp 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 mangaplus.shueisha.co.jp 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.

Last verified
3h ago
Latest check
6/6 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a cross-language manga tracker using list_manga language and status filters to surface new serializations per region.
  • Render a chapter reader app using the get_chapter pages array with encryption_key, width, height, and page_type fields.
  • Monitor new releases by polling get_updates and filtering update_groups by days_ago to detect same-day chapter drops.
  • Populate a manga discovery feed using get_featured title_lists grouped by magazine or genre.
  • Track popularity trends by recording score and rank from get_ranking across Hottest, Trending, and Completed tabs over time.
  • Filter MANGA Plus Creators (user-submitted / award) content separately from mainstream titles using the label=CREATORS parameter in list_manga.
  • Sync a database of series metadata — including number_of_views, rating, update_timing, and chapter counts — by iterating get_manga over title IDs.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does MANGA Plus have an official public developer API?+
No. Shueisha does not publish a public developer API or documented developer portal for MANGA Plus. This Parse API provides structured access to the same data available on the public site.
What does get_chapter return, and what is the encryption_key field for?+
get_chapter returns an ordered pages array where each entry includes an image_url, width, height, page_type (SINGLE, LEFT, RIGHT, or DOUBLE), and an encryption_key. MANGA Plus page images are XOR-encoded, and this hex key is what you use to decode each page image before display. The endpoint also returns last_page with the next_chapter id (null at series end) and next_timestamp.
Does list_manga paginate, and can I filter by genre tag?+
list_manga returns the entire status tab in one call with no pagination. The response includes an all_tags array with every genre tag available on the site, but the endpoint itself does not accept a tag filter parameter — tag-based filtering would need to be applied client-side against the returned manga array.
Does the API expose user accounts, reading history, or bookmarks?+
No. The API covers public catalog data: title metadata, chapter page images, rankings, featured lists, and update feeds. User account data, reading history, bookmarks, and comment threads are not exposed. You can fork this API on Parse and revise it to add any endpoint covering data accessible without authentication.
Are all language editions of a title returned by a single get_manga call?+
A single get_manga call returns one language edition identified by its title_id. The title object includes a language field, and the detail record references sibling edition IDs through title_languages. To retrieve another language edition's chapter list or metadata, call get_manga again with that edition's title_id. You can fork this API on Parse and revise it to batch multiple editions in one request if needed.
Page content last updated . Spec covers 6 endpoints from mangaplus.shueisha.co.jp.
Related APIs in EntertainmentSee all →
mangaupdates.com API
Track manga releases by day, look up detailed series information and genres, and monitor site statistics — all from MangaUpdates. Access release schedules, series metadata, and platform insights to stay updated on the latest manga.
comics.inkr.com API
Access data from comics.inkr.com.
karikari.app API
Search and discover webcomics, manga, and HQ titles available on KariKari, Brazil's leading comics platform. Find exactly what you're looking for by browsing their catalog of graphic novels and digital comics content.
cgccomics.com API
Access data from cgccomics.com.
webtoons.com API
Search and discover Webtoon series by title or genre, view episode details and images, check rankings and trending content, and learn about authors and their works. Access comprehensive information about original and canvas series to find your next favorite read.
tapas.io API
Look up detailed information about any comic or novel on Tapas.io to view titles, cover images, reader statistics, author names, and story synopses all in one place. Perfect for discovering new series or getting comprehensive details about your favorite Tapas stories.
animecorner.me API
Stay updated on the anime world by fetching the top anime news stories of the week and browsing the latest articles from Anime Corner. Discover trending posts and breaking news in the anime community all in one place.
tanogibi.com.br API
Look up comprehensive information about manga, light novels, and comics hosted on Tá No Gibi, the popular Brazilian webcomic platform. Get instant access to detailed title metadata and publication information for any series available on the site.