Create a private table from a CSV or the API, then join it with Allium data in your queries.
Upload a CSV or insert rows through the API to create a table only your organization can query. Join it with Allium data in any query, such as a list of wallets against balances or token contracts against stablecoin supply.Uploading needs the admin or user role in your organization.
In Allium App, open Library > Your Data and choose Upload Data.
2
Name the table and choose a file
Enter a table name and choose a CSV with a header row. Without a name, the table takes the file’s name.
3
Upload
Choose Upload. The table is ready to query once its rows are ingested.
A watchlist of stablecoin contracts with a segment column
Column names are lowercased, and any character other than a letter or number becomes an underscore. Column types are inferred from the data: dates and times load as timestamps, numbers as numbers, and everything else as text.
Insert Rows on a table’s page adds rows from another CSV or through the API. Overwrite replaces every row in the table instead, and can’t be undone. Each upload’s status and row count stay in the table’s upload history.
Send rows as a list of objects. The first request to a new table name creates the table, and "overwrite": true replaces its rows. Requests need an API key.
Your tables live in your organization’s database, at ORG_DB__<organization id>.default.<table>. In the query editor, the schema browser lists them under Your Uploaded Tables and inserts the full name.
Join the watchlist with stablecoin supply to get each contract’s latest circulating supply:
select w.segment, s.token_symbol, s.circulating_supply_usdfrom ORG_DB__<organization id>.default.stablecoin_watchlist wjoin stablecoins.core.supply_daily s on s.chain = w.chain and s.token_address = w.token_addresswhere s.date = (select max(date) from stablecoins.core.supply_daily)order by s.circulating_supply_usd desc
