You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
The informative endpoints all carry data points, but we also ned endpoints that can be consumed by the frontend that modify or update data.
POST /market/items - Post a new item to the market. This is associated with a user's data.
GET /market/items/{id}/buy - Trigger a 'buy item' request. The headers that are associated with this are the users' information. It sends back a 200 OK along with confirmations that the payment has gone through.
GET /market/items/{id}/remove - Triggers a 'remove item' request. This should authenticate with the user to check if they are indeed the owner of the item.
The text was updated successfully, but these errors were encountered:
If we are taking away the market, I don't think that most of these end points are needed. Why build these in when they're just going to be removed.
We just need endpoints for changes in the steads ( powder etc...) and giving items.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The informative endpoints all carry data points, but we also ned endpoints that can be consumed by the frontend that modify or update data.
/market/items
- Post a new item to the market. This is associated with a user's data./market/items/{id}/buy
- Trigger a 'buy item' request. The headers that are associated with this are the users' information. It sends back a 200 OK along with confirmations that the payment has gone through./market/items/{id}/remove
- Triggers a 'remove item' request. This should authenticate with the user to check if they are indeed the owner of the item.The text was updated successfully, but these errors were encountered: