api.example.com/v1/q4
Endpoint
One link, any feed.
Paste a public URL or a private one. Donum talks to it from the workspace, not from the browser.
Live Data
A URL, becomes a source.
Pull on demand. Watch the page redraw.
https://api.example.com/v1/q4?key=•••••••
Parser · auto · CSV detectedLast refresh 12s ago
Refresh log1 of 1
- +0sConnecting to api.example.com
- +0.2sTLS handshake ok
- +0.6sGET /v1/q4 · 200 OK
- +0.7sParsed 312 rows · 8 columns
- +0.8sReplaced source · charts redrawn
The shape
Three formats, one parser.
Point at any feed. The parser picks the format from the response and lays the rows in.
// CSV, the simplest case.GET https://api.example.com/v1/q4.csvRegion,Q1,Q2,Q3,Q4North,12400,14800,16200,18900// JSON, three shapes accepted.[ { region: "North", q1: 12400, ... } ]{ data: [ ... ] }{ rows: [ ... ] }
Auto detect
The right parser, every time.
Content type guides the choice. CSV, TSV and JSON each land as a typed grid with column inference.
- Numeric columns clean dollar marks, commas and spaces. The parser keeps strings when in doubt.
- Headers de duplicate. A second Region becomes Region two so charts stay legal.
- Twenty second timeout, five megabyte cap, server side fetch. The browser never touches the URL.
Three knobs
Endpoint, header, cadence.
A URL, an optional header, and a click. The page stays current.
Authorizationstays on the server. The browser never sees it.
Auth
Headers stay private.
Bearer tokens, API keys, custom headers. They live on the server. The frontend never receives the secret.
since last pull
Cadence
Manual, today.
Click Refresh whenever you want fresh rows. Scheduled cadences land in a future phase, sitting on the same engine.
The contract
Live without, loose ends.
20s
timeout per pull
5MB
payload cap
0
tokens in the browser
A workspace stays responsive when the worst feed misbehaves. The cap, the timeout, and the parse errors return clear codes. The grid keeps showing the last good rows.
In short
Questions, answered.
What kind of URLs work?+
Anything that returns CSV, TSV, or JSON. Auto detection picks the parser. JSON arrays, data wrapped, and rows wrapped all land cleanly.
Where do auth headers live?+
On the server. Donum makes the call from the workspace, not the browser. The token never reaches the client.
Is there a payload cap?+
Five megabytes per pull and a twenty second timeout. Both keep the workspace responsive.
Will charts redraw automatically?+
Yes. Every chart bound to the source updates the moment the new rows arrive.