en.onepiece-cardgame.com APIen.onepiece-cardgame.com ↗
Access card data, product listings, events, and news from the official One Piece Card Game site via 7 structured JSON endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/d95a69ed-8e8c-4298-a782-fe16e8b84f09/get_card_series' \ -H 'X-API-Key: $PARSE_API_KEY'
Extract all available card sets (series) with their unique IDs used for filtering cards in the get_cards endpoint.
No input parameters required.
{
"type": "object",
"fields": {
"data": "array of series objects with series_id and series_name",
"status": "string, always 'success'"
},
"sample": {
"data": [
{
"series_id": "569302",
"series_name": "PREMIUM BOOSTER -ONE PIECE CARD THE BEST vol.2- [PRB-02]"
},
{
"series_id": "569101",
"series_name": "BOOSTER PACK -ROMANCE DAWN- [OP-01]"
}
],
"status": "success"
}
}About the en.onepiece-cardgame.com API
This API exposes 7 endpoints covering the full official One Piece Card Game data catalog — cards, sets, products, events, news, and deck recommendations. The get_cards endpoint supports multi-dimensional filtering by color, series, card category, block icon, and keyword, returning paginated results with fields like power, counter, cost, attribute, effect text, and rarity. get_card_detail lets you pull granular stats for any individual card by its ID.
Card Data and Filtering
The get_cards endpoint accepts a POST request with optional filters: colors (comma-separated values such as Red, Blue, or mix), series (a series ID retrieved from get_card_series), categories (Leader, Character, Stage, or Event), block_icon (1–4), freewords for keyword search, and reprintsFlag to suppress reprint cards. Results are paginated via page and limit parameters. Each card object in the response includes id, name, rarity, category, cost, attribute, power, counter, color, block_icon, type, effect, and card (artwork reference).
Series, Products, and Deck Recommendations
get_card_series returns all available set IDs and names, which feed directly into the series filter on get_cards. get_products lists official releases — booster packs, starter decks, and accessories — with name, category, release_date, and image_url. get_recommended_decks returns officially published deck recipes with name, description, url, and image_url, sourced from the official site's strategy content.
Events and News
get_events returns upcoming and past events with title, date, category, url, and image_url. get_news provides the latest official announcements with title, date, category, and url. Both endpoints require no input parameters and reflect the current state of the official en.onepiece-cardgame.com site.
- Build a card search tool that filters by color and card type using
get_cardswith thecolorsandcategoriesparameters. - Populate a card database with full stats — power, counter, cost, effect text — retrieved from
get_card_detailby card ID. - Track official product release dates for booster packs and starter decks using
get_products. - Display upcoming tournament and event listings in a community app using
get_events. - Surface official deck recommendations and strategies to players using
get_recommended_decks. - Keep a news feed updated with official One Piece Card Game announcements via
get_news. - Map every card to its series by combining
get_card_seriesIDs withget_cardsseries filtering.
| 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 | 250 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 the official One Piece Card Game site have a public developer API?+
How does get_card_detail differ from get_cards when looking up a specific card?+
get_card_detail takes a single card_id parameter (e.g. OP01-001) and returns the first exact match with the full detail object including effect, attribute, counter, and block_icon. get_cards is designed for filtered browsing across the full catalog and returns a paginated array, making get_card_detail the right choice when you already know the card ID.What is the pagination behavior of get_cards, and are all filter results available at once?+
page and limit parameters to simulate pagination over those results. This means the full filtered set is available, but very broad queries (no filters, large sets) may return large payloads before pagination is applied.Does the API expose card price or secondary market data?+
Is card artwork or full image data returned by the API?+
card field in card detail responses contains a reference to card artwork, and get_products, get_events, and get_recommended_decks each include an image_url field. However, the card listing in get_cards does not currently include a per-card image URL at the list level. You can fork this API on Parse and revise the response mapping to surface image URLs in card list results.