Common Types
Common types and objects that the API uses
For data fetching API calls the params will consists of a condition, order by, and pagination info params. Every response returned by the client is a promise.
Condition
The condition param is specific to the corresponding API.
String Input Arg
For some of our api calls that require searching, we now support fuzzy matching or exact match.
Order Config
Sorting is handled by the orderBy param which is a OrderConfig type. Each API that accepts this config will have fields that are sortable (e.g. floor_price etc).
Pagination Info
For APIs with many responses we support pagination input. Our docs will specify which API has paginated results. Keep in the mind the limits of how much you can request.
For performance, we now have a progressive_load flag. This flag enables faster response time by skipping the count querying (will not return a valid total_page_number value) and returns true for has_next_page until there are no results.
Marketplace Action Response
Any action that interacts with the marketplace will return MarketPlaceTxOutput object. This consists of a data buffer that needs to be signed by the user and then sent to the chain via RPC. In addition there is an optional error object that returns.
Last updated