A single API call is a snapshot of one moment. Most of the time that is exactly what you want. But some questions are not one-time: what were the prices this week, how did this list change since Monday, is my dashboard current right now. For those, a call you have to remember to re-run is the wrong tool. Datasets is the right one.
A call is a moment. A dataset is a record.
A dataset is a saved result. You run any endpoint in the catalog, like you always do, and instead of the JSON scrolling past in your terminal, you keep it: named, stored, and yours to come back to. Same clean, structured response, now with a memory attached.
That alone is useful. The moment data has a home, you can point a dashboard, a sheet, or a teammate at it without anyone re-running anything or wondering whether they are looking at today’s numbers or last week’s.
Kept fresh, on your schedule
The part that turns a saved result into a living one is the schedule. Give a dataset a refresh cadence and it re-runs itself and keeps the latest, so the thing you saved is never stale. You do not host a cron, stand up a worker, or wire any of it together. You choose how often, and it stays current between visits.
Because every refresh is a real run, you always know how fresh the data is. When it last updated is right there next to it, so “is this current?” stops being a question you have to investigate.
A dataset rides on the same versioned contract as the endpoint under it. Pin a version and your saved shape holds run after run; track the active one and each refresh brings the latest repairs. Either way, the columns you built on do not move without you choosing it.
Yours to take anywhere
A record you cannot get out of the building is not much of a record. Every dataset exports on demand: pull the whole thing as JSON to feed a service, or as CSV to drop straight into a spreadsheet or a notebook. The clean shape you get from the API is the clean shape you export, no reshaping in between.
Who this is for
If your relationship to a source is “check on it regularly” rather than “call it once,” Datasets is built for you. It is the natural home for the pricing analyst, the ops person watching for changes, and anyone who would rather open a table that is already current than remember to go refresh it. It is one of the things people quietly build on us the most.
Pick a source in the catalog, run it once, and save the result as a dataset from your dashboard. Set a cadence, and the next time you look, it is simply up to date.
Started maviapi after one too many 2am scraper fires. Writes about the product, the bets behind it, and the parts of running an API company nobody warns you about.
More from Musab
