Get what the current user must accept, and whether they have.
Called on sign-in. `accepted: false` is the signal to show the acceptance prompt; nothing else needs to be interpreted. An environment with no published document set configured reports `accepted: true` with no documents, so a missing configuration cannot lock anyone out.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Response Body
curl -X GET "https://api.fruxon.com/v1/users/me/terms"{
"version": "string",
"accepted": false,
"documents": [
{
"name": "string",
"title": "string",
"url": "string"
}
]
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Sign out everywhere.
Ends every console session the caller has begun, on every device, including the one making this call. From then on the API answers any of those sessions with `401 {"error": "session_revoked"}`, and Firebase stops refreshing them. The caller should sign out locally when this succeeds; signing in again starts a session that is unaffected. Takes effect at once on the instance that answers, and on every other API instance within a minute. Personal access tokens and CLI keys are not affected: revoke those on their own page. Call it on the bootstrap host, like the rest of `users/me`. A 5xx after the revocation was recorded means Firebase could not be confirmed to have stopped refreshing the old sessions. The API refuses them regardless, but the caller's own session is refused too, so to complete the revocation, sign in again and repeat the call. The later instant covers the earlier one.
Record the current user's acceptance of the published legal documents.
The request states which version is being accepted, echoed from the GET. A version that is not current is rejected, so a stale browser tab cannot accept superseded documents and be counted as current. Acceptance is appended, never updated: accepting twice — after a version bump, or from a second device — writes a second row, because both are real events and this record is evidence rather than a flag. The caller's IP and user agent are recorded alongside, as evidence of consent.