SoulFire LogoSoulFire

List users

Lists all users in the system.

GET
/v1/users

Lists all users in the system.

Authorization

AuthorizationBearer <token>

Preferred API authentication. Use a JWT with the api audience.

In: header

Response Body

application/json

application/json

application/json

application/json

curl -X GET "http://127.0.0.1:38765/v1/users"
{
  "users": [
    {
      "id": "string",
      "username": "string",
      "role": "ADMIN",
      "email": "string",
      "created_at": {
        "seconds": 0,
        "nanos": 0
      },
      "updated_at": {
        "seconds": 0,
        "nanos": 0
      },
      "last_login_at": {
        "seconds": 0,
        "nanos": 0
      },
      "min_issued_at": {
        "seconds": 0,
        "nanos": 0
      }
    }
  ]
}
{
  "code": 0,
  "grpc-code": "string",
  "message": "string",
  "stack-trace": "string",
  "details": [
    {}
  ]
}
{
  "code": 0,
  "grpc-code": "string",
  "message": "string",
  "stack-trace": "string",
  "details": [
    {}
  ]
}
{
  "code": 0,
  "grpc-code": "string",
  "message": "string",
  "stack-trace": "string",
  "details": [
    {}
  ]
}

How is this page?

Update server config entry PUT

Updates a single configuration entry identified by namespace and key. This is a granular update operation for modifying individual settings. This is the preferred method for real-time UI interactions where users modify settings one at a time. It avoids overwriting unrelated settings and is more efficient than replacing the entire configuration. If the namespace doesn't exist, it will be created. If the key doesn't exist within the namespace, it will be added. Existing values are overwritten. The change is persisted to the database, and runtime hooks are triggered to apply the new value immediately where applicable.

Create user POST

Creates a new user account in the system.