Who holds this token
Start here. The person behind the token, the token itself (its kind, scopes and when it runs out), and every family or business it could name in the Thaw-Account header. Nothing here changes with that header; where a call landed is GET /account.
WWW-Authenticate names the resource metadata document.scope and in the WWW-Authenticate header as insufficient_scope; a plan that does not come with it says which one does.familybusinessownermemberviewervieweditupload_onlycurl "https://api.thawed.app/v1/identity" \
-H "Authorization: Bearer $THAW_TOKEN"{
"user": {
"id": "019958a0-3e60-7f5c-9d41-5b2e4c80af33",
"name": "Marisol Alvarez",
"email": "marisol@example.com"
},
"token": {},
"accounts": [
{
"id": "019958a0-2d5f-7e4b-8c30-4a1d3b7f9e22",
"name": "The Alvarez family",
"kind": "family",
"role": "owner",
"guest": false
}
],
"header": "Thaw-Account",
"api": "https://api.thawed.app/v1"
}