Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.1] Create /catalog endpoint #228

Open
flobarreto opened this issue Feb 17, 2023 · 0 comments
Open

[1.1] Create /catalog endpoint #228

flobarreto opened this issue Feb 17, 2023 · 0 comments
Assignees

Comments

@flobarreto
Copy link
Contributor

Nowadays we’ve two requests to get assets, the one that picks items and the one that picks nfts.

We need to have one new request (get) that brings all items paired with the nfts for this items

We’ll want to conserve the current endpoints for items (/items) and NFTs (/nfts) so we don’t introduce breaking changes for third parties consuming them. Having said that, we still need a new way to consume the grouped data. We’ll need a new endpoint that retrieves the data needed to create the “catalog” for the listing pages.

Create an endpoint /catalog that returns the data needed for rendering the unified cards. Let’s call those object listings. At the same time, it should support all of the current filters.
- Data needed in the response:
- Item fields:
- name
- creator
- minting info
- available (to show stock)
- price for minting
- listings info
- how many listings there are
- price range (low to max)
- rarity
- category
- body shape
- Supported status filters:
- Available for sale
- available > 0
- order > 0
- only available for minting
- available > 0
- order = null
- only listings
- available = 0
- order > 0
- not for sale
- available = 0
- order = null

@juanmahidalgo juanmahidalgo self-assigned this Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants