Read APIs
Use the Public Read API for data retrieval without creating purchases, shipments, listings, or other side effects.
https://www.dyli.io/api/public/v1
All endpoints require an API key. The endpoint index at GET /overview reports live status and documentation URLs.
Base and refreshed pack artwork
Existing keys, endpoint paths and response field names remain compatible. New integrations can use /packs; /boxes remains an alias. Refresh cached pack artwork from the returned image fields and preserve its aspect ratio.
Read-only integrations do not need a payment or signing flow. If you cache contract or network data, refresh it through /contracts; if you query holdings by wallet address, use the collector's current Base wallet. Historical transaction references retain their original chain. Treat those addresses and returned values as data that can change, rather than constants in your integration.
Catalog and platform
| Method and path | Returns |
|---|---|
GET /overview | Live endpoint inventory and controls. |
GET /search | Product discovery by text, taxonomy, identifiers, and availability. |
GET /products/{productId}/cert | Grading certificate, creation date, and price for one product ID. |
GET /contracts | Current public contract references. |
GET /metadata/{tokenId} | Basic product metadata and market context. |
GET /metadata/advanced/{tokenId} | Rich metadata for one token. |
GET /metadata/advanced | Rich metadata for up to 50 token IDs. |
POST /metadata/advanced | The same read-only batch lookup with token IDs in JSON. This does not mutate data. |
Marketplace activity
| Method and path | Returns |
|---|---|
GET /listings | Active DYLI primary and secondary inventory. |
GET /ebay/listings | Approved live eBay inventory, including PSA Vault. |
GET /offers | Active or accepted secondary offers. |
GET /sales | Normalized sale and lifecycle activity. |
GET /redemptions | Completed shipping, ripping, and grading redemptions. |
GET /p2p-trades | Completed collector-to-collector trades. |
Read API prices are discovery data. Use the Commerce API to obtain partner-filtered purchase instructions and a server-priced quote.
Users and collections
| Method and path | Returns |
|---|---|
GET /users/{identifier} | Basic public profile and wallet information for any collector. |
GET /users/{identifier}/diamonds | Current diamond balance, username, numeric DYLI user ID, wallet and avatar. See Diamonds. |
GET /diamonds/leaderboard | Paginated diamond balances with username, numeric DYLI user ID, wallet, avatar and rank. |
GET /sellers/{identifier} | Seller profile, products, and Packs by username or wallet. |
GET /holdings/{identifier} | Current token holdings by username or wallet. |
GET /sets/{collection} | Set catalog and collector progress. |
GET /sets/{collection}/{setCode} | Cards and ownership state for one set. |
GET /sets/{collection}/{setCode}/missing | Missing cards with optional availability and price filters. |
Experiences, verification, and analytics
| Method and path | Returns |
|---|---|
GET /packs and GET /packs/{boxId} | Pack catalog or one Pack. |
GET /packs/{boxId}/ranges | Odds ranges, active contents, and inventory count/value totals. |
GET /packs/{boxId}/history | Cursor-paginated pull history. |
GET /packs/verify | Completed Pack result verification. |
GET /fair-drops | Current and historical Fair Drops. |
GET /fair-drops/{identifier}/verify | Fair Drop verification. |
GET /digital-packs | Digital pack product stats and activity. |
GET /transactions | Transaction totals by time period. |
GET /rewards | Rewards leaderboards. |
GET /referrals | Refer & Earn program start and current rates. |
White-label reads
Partner-filtered catalog routes are available under /api/commerce/v1/catalog/*, including listings, Packs, redemptions, approved eBay inventory, collections, Fair Drops, digital packs, and search.
Use these routes when an app needs a limited or branded catalog. Saved configuration will be available with the Commerce API.
Common behavior
- Use Filtering for taxonomy and market filters.
- Use Pagination for page and cursor conventions.
- Use Errors for status codes and retry behavior.
- Read routes require a
read,commerce, orwritescope.