Every endpoint
42 endpoints under https://api.thawed.app/v1, in 9 sections. Every one takes a bearer token, and every refusal is a problem you can read out loud.
#You
Who the token is, and where it may act.
#Documents
What is on file: listed, searched, opened with a window of its words, added, filed as something else, moved, linked to people and things, shared out. A change needs the `write` scope; adding one needs the role and the scope but not the plan.
#Facts
What Thaw took off the pages, with sums. Account, policy and license numbers come only with the `identifiers` scope.
#People & things
Who and what the documents are about: people, pets, vehicles, homes, accounts, policies, companies. Renamed, combined and answered here as on the page.
#Checkup
Everything that needs a person, in one shape: the dated items and what is missing, each handled, snoozed or dismissed here as on the page.
#Bundles
A named set of documents, made by hand, and the year-end tax package Thaw assembles from a rule.
#Imports
A previous system's export, a cloud folder or a mailbox brought in, with where each stands.
#Uploads
A large file in parts, straight to storage, the way the browser sends anything past the plain upload limit and every archive.
#Ask
Thaw's answer to a question, streamed as server-sent events, and the email drafts. Each one counts as an ask on the plan. Needs the `ask` scope.
Shapes
The named shapes an answer is made of: a document, a fact, a person or thing, a Checkup item.