/v2/users HTTP routes from your backend with x-builder-api-key. The wallet address is a filter. These reads require no wallet signature or wallet access token. Query the address that holds the cards. A person’s signer and their contract wallet can have different collections.
Show the collection
Page throughcollectibles with limit and offset. The summary covers the same cards as the unfiltered list. Once the wallet owns a card on chain, it appears regardless of where the wallet acquired it. Undelivered draws are visible only to the selling builder.
Read pull for details of a card the wallet drew through your integration. For other owned cards, including draws through another builder, the field is null.
Use state.status to decide which action to show.
To look up specific cards, pass up to 20 distinct decimal token IDs as
?tokenIds=1,2 or ?tokenIds=1&tokenIds=2. The list and pagination.total include only matches. The separate wallet summary still covers the whole collection.
Page through activity
The activity feed can include on-chain events outside your builder’s sales. UsenextCursor from one response as the next request’s cursor. Continue through an empty page if it has a cursor. Stop when nextCursor is null. A transaction can contain several events and span multiple pages.
Use wallet pull history when you need draws attributed to your builder. Use Redeem for private shipping information.