The routes behind the TellersWindow API
The dashboard reads these JSON routes. There is no key to request and no account to open: the data behind them is the workspace file, apart from the one live price call the feed reports on.
60 / 10
Rate limit per route, read / write
None
Authentication
REST
JSON API
API Reference
Every route the dashboard reads, with the shape of the body it returns.
Portfolio summary — total value, day change, allocation and holdings. ?section=allocation, ?section=holdings, ?section=series or ?section=workspace returns one part.
No authentication
No route here asks for a token. There is no key to generate, no OAuth flow and no account to open — the data behind every route is the workspace file, and the only live market call is the price feed's.
Accept: application/json
Rate Limits
60 requests per minute per client on each read route, 10 on each write route, each over a 60-second window. Every route has its own budget, so browsing one cannot spend another’s, and there is no key, no tier and no plan behind it.
Error Shape
Every failure returns the same envelope: success false, an error code, a message, a timestamp.
One call is the whole client
No package to install and no library to publish — the routes speak plain JSON over HTTP. Base URL: tellerswindow.vercel.app
Node.js
Python
Go
Open the dashboard. Nothing to sign up for.
No API key, no tier, no plan — the dashboard opens straight onto the routes documented here.