Riftbound

Expansions

The expansion object

Information about Riftbound expansions.

id <string>

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

name <string>

The name of the expansion (e.g., "Origins").

type <string>

The type of expansion (e.g., "Main").

code <string>

The code for the expansion.

total <integer>

The total number of cards in the expansion.

printed_total <integer>

The number of cards printed in the set.

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": "OGN",
  "name": "Origins",
  "type": "Main",
  "code": "OGN",
  "total": 352,
  "printed_total": 298,
  "release_date": "2025/10/31",
  "logo": "https://images.scrydex.com/riftbound/OGN-logo/logo",
  "language": "English",
  "language_code": "EN"
}
Example Requests
curl -X GET 'https://api.scrydex.com/riftbound/v1/expansions/OGN' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'X-Team-ID: YOUR_TEAM_ID'

Get an expansion

Retrieve details about a specific Riftbound expansion.

URL

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

Example request:

Example Requests
curl -X GET 'https://api.scrydex.com/riftbound/v1/expansions/OGN' \
  -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 "origins" in the name field: name:origins
  • Search for the phrase "Origins" in the name field: name:"Origins"

Wildcard Matching

  • Expansions where the name starts with "ori": name:ori*

Exact Matching

  • Match expansions where the name is exactly "Origins": !name:"Origins"

Range Searches

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

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": "OGN",
      "name": "Origins",
      "type": "Main",
      "total": 352,
      "language": "English",
      "language_code": "EN",
      "release_date": "2025/10/31"
    }
  ],
  "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.