Skip to main content

Contracts

GET /api/public/v1/contracts

Returns the live DYLI public contract map.

Use this when your integration needs contract addresses for tokens, boxes, Fair Drops, secondary marketplace activity, P2P trading, or settlement tokens. The endpoint returns the public contract map builders actually need, without app internals.

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

Contract Groups

GroupWhat it means
live_contractsFlat list of the public contracts DYLI exposes to builders.
nft_contractsERC-1155 inventory contracts for DYLI item ownership.
marketplace_contractsSecondary marketplace contracts used for listings and accepted offers.
box_contractsBox-opening contracts used for pack-style pull experiences.
fair_drop_contractsFair Drop contracts used for entry and verification flows.
p2p_trading_contractsCollector-to-collector trading contracts.
pricing_contractsSettlement token context, currently USDC.e for secondary flows.

Each contract row includes the name, role, type, address, chain, and chain id.

Example Response

{
"name": "DYLI Contracts",
"version": "1.0",
"network": {
"name": "Abstract",
"chain_id": 2741
},
"live_contracts": [
{
"name": "DYLI ERC-1155 Inventory",
"role": "main_tokens",
"type": "erc1155",
"address": "0x...",
"chain": "abstract",
"chain_id": 2741
}
]
}

Notes

Contracts are useful context, but the public API should still be your first stop for normalized product, listing, sale, trade, box, and verification data. The API already turns raw app and chain activity into fields that are easier to work with.