Multiple Tokens' Valuations

post

https://example.com/token-valuations

For each contract-token pair, corresponding valuation will be returned. If the token is not in our system, it will return 404 (even if 1 of all tokens you provided is missing) with more detail on which one. It's recommended to ignore missing entries and cross reference in your local code to see which ones are missing.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

Timestamp

int64

Retrieve valuations based on the given timestamp's date Note: since valuations are currently on a daily basis, only the date component of the time (irrespective of the hour) will be used. If no value is passed, by default it will take the current valuation.

ValuationMethod

string

enum

The valuation method to use (in case timestamp is provided, otherwise this will have no effect)

Closest: Returns the closest recorded valuation to the given timestamp, including snapshots after the given timestamp.
ClosestBefore: Returns closest recorded valuation before the given timestamp, but only considers snapshots before the given timestamp

Allowed:

IgnoreMissingEntries

boolean

Defaults to false

Whether it should skip missing tokens / valuations instead of showing 404

Body Params

Contract Address - Token Index pairs for which you wan to have the valuation

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200OK

400Bad Request

404Not Found