Quickstart

Set your API key as an environment variable:

export DYLI_API_KEY="dyli_live_..."

Fetch active listings:

curl "https://www.dyli.io/api/public/v1/listings?page=1&pageSize=10" \
  -H "x-api-key: $DYLI_API_KEY"

Search products:

curl "https://www.dyli.io/api/public/v1/search?q=pokemon&onlyListed=true" \
  -H "Authorization: Bearer $DYLI_API_KEY"

Fetch token metadata:

curl "https://www.dyli.io/api/public/v1/metadata/12345" \
  -H "x-api-key: $DYLI_API_KEY"

Keep API keys in server-side code. Do not include them in public frontend code.

Base Paths

API	Production base path
Read	`https://www.dyli.io/api/public/v1`
Commerce	`https://www.dyli.io/api/commerce/v1`
3PL	`https://www.dyli.io/api/3pl/{company}`

Use the environment-specific host for staging or preview deployments.

For a complete single-file contract, open Markdown references. It includes standalone Read, Commerce, and 3PL files plus the Commerce OpenAPI document.

Next, choose Read APIs, the live Commerce API, or the 3PL API.

Base Paths​

Base Paths