One Piece

Expansions

The expansion object

Information about One Piece expansions.

id <string>

The unique identifier for the expansion (e.g., OP13).

name <string>

The name of the expansion (e.g., "Carrying On His Will").

type <string>

The type of expansion (e.g., "Booster Pack").

code <string>

The code for the expansion.

total <integer>

The total number of cards in the expansion.

release_date <string>

The release date of the expansion (YYYY/MM/DD).

logo <string>

URL for the expansion logo.

language <string>

The language of the expansion.

language_code <string>

The language code of the expansion.

Example JSON representation of an expansion:

{
  "id": "OP13",
  "name": "Carrying On His Will",
  "type": "Booster Pack",
  "code": "OP13",
  "total": 120,
  "release_date": "2025/11/07",
  "logo": "https://images.scrydex.com/onepiece/OP13-logo/logo",
  "language": "English",
  "language_code": "EN"
}

Example Requests

Lang:

curl -X GET 'https://api.scrydex.com/onepiece/v1/expansions/OP13' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'X-Team-ID: YOUR_TEAM_ID'

Get an expansion

Retrieve details about a specific One Piece expansion.

URL

GET https://api.scrydex.com/onepiece/v1/expansions/<id>

Example request:

Example Requests

Lang:

curl -X GET 'https://api.scrydex.com/onepiece/v1/expansions/OP01' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'X-Team-ID: YOUR_TEAM_ID'

Search expansions

Fetching and searching for multiple expansions in the Scrydex API is simple yet powerful.
Use the various query parameters to customize your requests and retrieve the specific cards or data you need.

Query Parameters

All query parameters are optional, but combining them allows for advanced and targeted searches.

Note that all query parameters can be used with snake case or camel case (so pageSize or page_size are both acceptable).

Parameter	Description	Default Value
q	A search query for advanced filtering. Examples can be found below.	-
page	The page of data to access.	`1`
page_size	The maximum number of cards to return per page. The highest allowable value is `100`.	`100` (max: `100`)
select	A comma-delimited list of fields to return in the response (e.g., `?select=id,name`). If omitted, all fields are returned.	-

Key Features of `q` (Search Queries)

Search queries use a Lucene-like syntax for filtering, making it easy to build powerful card searches.
Below are examples of supported query operations:

Keyword Matching

Find expansions that contain "romance" in the name field: name:romance
Search for the phrase "romance dawn" in the name field: name:"romance dawn"
Combine multiple conditions:
- Expansions with the type "Booster Pack" and language "English" type:"Booster Pack" language:English

Wildcard Matching

Expansions where the name starts with "rom": name:rom*

Exact Matching

Match expansions where the name is exactly "Romance Dawn": !name:"Romance Dawn"

Range Searches

Fields containing numerical data (e.g., "total") support range searches:

Expansions with at least 100 cards: total:[100 TO *]

Pro Tip: Use square brackets [ ] for inclusive ranges, and curly braces { } for exclusive ranges.

Use the query parameters to retrieve and search expansions. Below are examples using Scrydex API:

Ordering Data

The orderBy parameter allows for flexible sorting of results:

Order expansions by name: ?orderBy=name
Order expansions by release date: ?orderBy=-release_date

Field Selection

Optimize and reduce response payload sizes using the select parameter to return only the fields you care about:

Example: Request only id and name fields: ?select=id,name

Response Example

Here’s a sample response for a search query:

{
  "data": [
    {
      "id": "OP01",
      "name": "Romance Dawn",
      "type": "Booster Pack",
      "total": 121,
      "language": "English",
      "language_code": "EN",
      "release_date": "2022/12/02"
    }
  ],
  "page": 1,
  "pageSize": 1,
  "totalCount": 1
}

Best Practices for Fetching & Searching

Paginate Results: Use the page and pageSize parameters to prevent overloading responses.
Limit Fields Returned: Use the select parameter to only get the data you need.
Avoid Overhead: Minimize wildcard or range queries for better performance.