Account

The account endpoint reports which clinic the calling key belongs to and which scopes it carries. It's the simplest way to verify a key works and to discover its permissions before making other calls.

#The account object

Field	Type	Description
`clinic_id`	string	The clinic this key belongs to.
`scopes`	string[]	The scopes this key can use.

#Introspect the current key

GET

Requires any valid key - no specific scope.

curl https://api.smile-app.co.il/v1/me \
  -H "Authorization: Bearer sk_live_..."

sc whoami

{
  "data": {
    "clinic_id": "demo",
    "scopes": ["patients:read", "appointments:read", "catalog:read"]
  }
}

Use this to fail fast

Call /v1/me at startup to confirm the key is valid and holds the scopes your integration needs - surface a clear configuration error rather than discovering missing scopes through scattered 403s later.