Sealed Products
The sealed product object
Each field available on a Riftbound sealed product is described below.
id <string>
The unique identifier for the sealed product.
name <string>
The name of the sealed product.
type <string>
The type of sealed product (e.g., "Booster Pack").
description <string>
A detailed description of the product.
images <array of maps>
Contains URLs for the product's images.
- type
<string>: The type of image. - small
<string>: The URL of the small image. - medium
<string>: The URL of the medium image. - large
<string>: The URL of the large image.
expansion <map>
Details about the expansion this sealed product belongs to.
- id
<string>: The unique identifier for the expansion. - name
<string>: The name of the expansion. - type
<string>: The type of expansion. - code
<string>: The code for the expansion. - total
<integer>: 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. - logo
<string>: URL for the expansion logo. - language
<string>: The language of the expansion. - language_code
<string>: The language code of the expansion.
language <string>
The language of the sealed product.
language_code <string>
The language code of the sealed product (e.g., "EN").
expansion_sort_order <integer>
The sort order of the sealed product within its expansion.
variants <array of maps>
A list of collectible variants of the sealed product.
- name
<string>: The name of the variant (e.g., "normal"). - prices
<array of maps>: Price data for this variant.
Example JSON representation of a Riftbound sealed product:
{
"id": "OGN-s1",
"name": "Origins Booster Pack",
"type": "Booster Pack",
"description": "Origins, the debut set of Riftbound: League of Legends TCG, brings Champions to the battlefield like never before...",
"images": [
{
"type": "front",
"small": "https://images.scrydex.com/riftbound/OGN-s1/small",
"medium": "https://images.scrydex.com/riftbound/OGN-s1/medium",
"large": "https://images.scrydex.com/riftbound/OGN-s1/large"
}
],
"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"
},
"language": "English",
"language_code": "EN",
"expansion_sort_order": 1,
"variants": [
{
"name": "normal",
"prices": [
{
"condition": "U",
"is_perfect": false,
"is_signed": false,
"is_error": false,
"type": "raw",
"low": 12.24,
"market": 13.32,
"currency": "USD"
}
]
}
]
}
curl -X GET 'https://api.scrydex.com/riftbound/v1/sealed/OGN-s1' \
-H 'X-Api-Key: YOUR_API_KEY' \
-H 'X-Team-ID: YOUR_TEAM_ID'
Get a sealed product
This endpoint retrieves a specific Riftbound sealed product by its unique identifier.
URL
GET https://api.scrydex.com/riftbound/v1/sealed/<id>
URL Parameters
- id
<string>
The unique identifier of the sealed product to retrieve (e.g.,OGN-s1).
Query Parameters
select
<string>
Comma-separated list of fields to include in the response.include
<string>
Related resources to include (e.g.,prices).
Example request to fetch a single sealed product:
curl -X GET 'https://api.scrydex.com/riftbound/v1/sealed/OGN-s1' \
-H 'X-Api-Key: YOUR_API_KEY' \
-H 'X-Team-ID: YOUR_TEAM_ID'
Search sealed products
Fetching and searching for multiple sealed products in the Scrydex API is simple yet powerful.
Use the various query parameters to customize your requests and retrieve the specific sealed products or data you need.
URL
There are two primary endpoints for fetching multiple sealed products: Searching across the whole database, or scoped to a specific expansion.
Get all sealed products (paginated), unfiltered:
GET https://api.scrydex.com/riftbound/v1/sealed
Get all sealed products (paginated), for a specific expansion:
GET https://api.scrydex.com/riftbound/v1/expansions/OGN/sealed
Both of these endpoints support the same query parameters and underlying search logic.
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 sealed products 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. |
- |
| include | Used to include additional data, such as prices. These are fields you opt-in to, and aren't included in the response by default. | - |
Key Features of q (Search Queries)
Search queries use a Lucene-like syntax for filtering, making it easy to build powerful sealed product searches.
Below are examples of supported query operations:
Keyword Matching
- Find sealed products that contain "origins" in the name field:
name:origins - Search for the phrase "Origins Booster Pack" in the name field:
name:"Origins Booster Pack"
Wildcard Matching
- Products where the name starts with "ori":
name:ori*
Exact Matching
- Match sealed products where the name is exactly "Origins Booster Pack":
!name:"Origins Booster Pack"
Searching Nested Fields
Leverage the . separator to search nested fields:
- Filter by expansion ID:
expansion.id:OGN
Example: Fetch & Search Sealed Products
Use the query parameters to retrieve and search sealed products. Below are examples using Scrydex API:
Ordering Data
The orderBy parameter allows for flexible sorting of results:
- Order sealed products by name:
?orderBy=name
Field Selection
Optimize and reduce response payload sizes using the select parameter to return only the fields you care about:
- Example: Request only
idandnamefields for all sealed products:?select=id,name
Response Example
Here’s a sample response for a search query:
{
"data": [
{
"id": "OGN-s1",
"name": "Origins Booster Pack",
"type": "Booster Pack"
}
],
"page": 1,
"pageSize": 1,
"totalCount": 1
}
Best Practices for Fetching & Searching
- Paginate Results: Use the
pageandpageSizeparameters to prevent overloading responses. - Limit Fields Returned: Use the
selectparameter to only get the data you need. - Avoid Overhead: Minimize wildcard or range queries for better performance.