
Compute Unit Cost
The Collectibles endpoint’s CU cost equals the number of chains you include via thechain_ids query parameter. If you omit chain_ids, we use the endpoint’s chains tagged default (currently chains, subject to change). See the Supported Chains page to learn about chain tags.
For example, ?chain_ids=1,8453,137 processes three chains and currently consumes three CUs. Omitting chain_ids uses the default set at request time and consumes CUs (equal to the size of that set).
Headers
Used for authenticating requests. Provide an API key with a purpose of Sim API. See Authentication.
Path Parameters
The wallet address to get collectibles for.
Query Parameters
Filter by chain(s). Accepts numeric chain IDs and/or tags. Provide a single value (e.g. ?chain_ids=1 or ?chain_ids=mainnet) or a comma-separated list (e.g. ?chain_ids=1,8543,testnet). Chain names are not accepted. If this query parameter is omitted, results include collectibles from chains with the default tag. See the Supported Chains Tags section.
Pagination cursor. Use the next_offset value from the previous response to get the next page. Omit to fetch the first page.
Maximum entries per page for collectibles. Default is 250 when not provided. Values above 2500 are reduced to 2500. If fewer entries exist than the limit, only the available entries are returned.
1 <= x <= 2500Response
A list of collectibles for the specified address.
The wallet address for which collectibles are being reported.
A list of collectible entries.
Timestamp of when the request was received.
Timestamp of when the response was generated.
Use this value as the offset in your next request to continue pagination. Not included when there are no more entries.