FilTracker's browser-facing API (filaments, usage, export) is authenticated by your session cookie and isn't designed for scripting against directly. The two endpoints below are the intentionally-public surface — stable, documented, and meant to be called from outside the browser.
/api/ingest/usageLogs usage against one of your spools. Generate a token and a ready-to-use script or webhook template from Integrations — this is what powers the slicer post-processing script and OctoPrint-Webhooks setup.
Authorization: Bearer <your token>
{
"filamentId": "spool-id-from-your-account",
"grams": 24.36,
"source": "slicer_estimate" // or "octoprint_webhook" — optional, defaults to slicer_estimate
}Returns { "ok": true } on success. 401 for a missing/invalid/revoked token, 404 if the filament doesn't exist or isn't yours, 400 if the spool doesn't have that much filament left, 429 if you're over 20 requests/minute on that account.
/api/tare?manufacturer=...Looks up a known empty-spool (tare) weight for a manufacturer, used to convert a gross scale reading into net remaining filament. No account needed — this is reference data anyone can query.
GET /api/tare?manufacturer=Prusament
{
"best": { "emptyWeightG": 193, "model": "PLA, 1kg", "sourceUrl": "...", "verified": true },
"history": [ /* every contributed value for this manufacturer, most-verified first */ ]
}best is null if nothing is known yet for that manufacturer — contribute a value from the "I weighed it" tab when logging usage on a spool of that brand.
Want your whole inventory instead?
Export your data as JSON or CSV any time — full-fidelity, no lock-in.