Users

GET /users

List every active org user for the API key's org, sorted by u.name ASC. Each entry is a org_users row joined against users, with the global users.id exposed as id and the org-membership row id exposed as org_user_id. Each entry also includes a nested webhook block (enabled, url, events, throttle_per_minute) but not has_secret — see the single-user GET for that. There is no pagination and no filter parameters on this endpoint — it returns the full active roster on every call.

Request example

curl -sS https://api.tasklife.com/v1/users \
  -H "Authorization: Bearer *** \
  -H "Content-Type: application/json"

Response 200 OK

The user array is nested under data.users[]:

{
  "success": true,
  "data": {
    "users": [
      {
        "id":               1042,
        "org_user_id":      318,
        "name":             "Alex Rivera",
        "email":            "[email protected]",
        "user_type":        "human",
        "handle":           "alex",
        "webhook": {
          "enabled":             true,
          "url":                 "https://hooks.acme.dev/tasklife/alex",
          "events":              ["task.created", "task.completed"],
          "throttle_per_minute": 30
        }
      },
      {
        "id":               1184,
        "org_user_id":      422,
        "name":             "Priya Shah",
        "email":            "[email protected]",
        "user_type":        "human",
        "handle":           "priya",
        "webhook": {
          "enabled":             false,
          "url":                 "",
          "events":              [],
          "throttle_per_minute": 30
        }
      },
      {
        "id":               1255,
        "org_user_id":      501,
        "name":             "Jordan Lee",
        "email":            "[email protected]",
        "user_type":        "human",
        "handle":           null,
        "webhook": {
          "enabled":             false,
          "url":                 "",
          "events":              [],
          "throttle_per_minute": 30
        }
      }
    ]
  }
}

Errors

This endpoint has no documented error cases beyond a missing/invalid API key (handled before the router reaches the users block).

{
  "success": false,
  "error": {
    "code":    "UNAUTHORIZED",
    "message": "Invalid or missing API key"
  }
}

GET /users/{org_user_id}

Fetch a single org-membership row by id, including the full webhook configuration with the has_secret flag. The path parameter is the org_users.id — the response surfaces both ids: data.user.id (global users.id) and data.user.org_user_id (org_users.id). The status field is included regardless of value (the list endpoint, by contrast, filters out inactive rows); the single-user GET does not apply the status = 'active' filter. Returns 404 if the id doesn't exist or belongs to a different org.

Path parameters

Request example

curl -sS https://api.tasklife.com/v1/users/318 \
  -H "Authorization: Bearer *** \
  -H "Content-Type: application/json"

Response 200 OK

The user is nested under data.user, with webhook config under data.user.webhook:

{
  "success": true,
  "data": {
    "user": {
      "id":               1042,
      "org_user_id":      318,
      "org_id":           42,
      "name":             "Alex Rivera",
      "email":            "[email protected]",
      "user_type":        "human",
      "department":       "Engineering",
      "role":             1,
      "status":           "active",
      "handle":           "alex",
      "webhook": {
        "enabled":             true,
        "url":                 "https://hooks.acme.dev/tasklife/alex",
        "events":              ["task.created", "task.completed"],
        "throttle_per_minute": 30,
        "has_secret":          true
      }
    }
  }
}

Errors

{
  "success": false,
  "error": {
    "code":    "NOT_FOUND",
    "message": "User not found"
  }
}

GET /users/{org_user_id}/teams

List every team a single org user belongs to. Rows come from team_user_assignments joined against teams, ordered by team_name ASC. The response is a two-key envelope: data.user (a freshly-fetched summary of the org user — same fields as fetchOrgUserForTeamAssignments()) and data.teams[] (the membership roster, an empty array if the user has none). The user lookup uses $activeOnly = true, so an inactive user returns 404 even if a team_user_assignments row exists for them.

Path parameters

Request example

curl -sS https://api.tasklife.com/v1/users/318/teams \
  -H "Authorization: Bearer *** \
  -H "Content-Type: application/json"

Response 200 OK

The user summary is under data.user and the team list under data.teams[]:

{
  "success": true,
  "data": {
    "user": {
      "org_user_id":         318,
      "org_id":              42,
      "user_id":             1042,
      "user_email":          "[email protected]",
      "department":          "Engineering",
      "role":                1,
      "is_section_manager":  1,
      "status":              "active",
      "name":                "Alex Rivera",
      "email":               "[email protected]",
      "display_name":        "Alex Rivera",
      "user_type":           "human"
    },
    "teams": [
      {
        "id":           17,
        "team_name":    "Mobile Platform",
        "shortcode":    "MOB",
        "color":        "#0d6efd"
      },
      {
        "id":           18,
        "team_name":    "Platform Infrastructure",
        "shortcode":    "PLAT",
        "color":        "#198754"
      }
    ]
  }
}

Errors

{
  "success": false,
  "error": {
    "code":    "FORBIDDEN",
    "message": "Org admin required"
  }
}