Verify that the calling credential is valid for this tenant.
Returns a diagnostic snapshot — auth scheme, tenant, user, API key name, granted scopes, and API-key expiry — so a client (e.g. `fruxon doctor`) can distinguish a working key from the various failure modes without touching a real resource: <list type="bullet"><item><b>401</b> — credential is missing or invalid.</item><item><b>403</b> — credential is valid but not bound to this tenant.</item><item><b>200</b> — credential is good; inspect the body for scopes / upcoming expiry.</item></list> Side-effect-free and excluded from rate limiting so the doctor command can run freely.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/auth/health"{
"authenticationSource": "NONE",
"tenantId": "00000000-0000-0000-0000-000000000000",
"userId": "string",
"email": "string",
"tokenName": "string",
"scopes": [
"string"
],
"tokenExpiresAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}List the API key scope vocabulary.
Returns every scope a key can carry (with its resource / action / intent breakdown) plus the named presets the mint endpoint accepts. Powers the dashboard mint flow and the CLI's `fruxon api-key-scopes list` command — clients shouldn't hardcode the vocabulary because that drifts the moment a new scope ships. No scope required: this is metadata anyone who can authenticate must be able to read (you can't mint a scoped key without knowing what scopes exist).
Gets authorization settings metadata for all supported auth types.
Returns the configuration parameters and their descriptions for each supported authorization type, used when creating or editing integrations.