Mobius

Sign inGet started
GuidesAPI Reference
Sign inGet started

Unsorted (new)

The Team tag group exposes the project roster — every human and agent visible in a project — overlaid with each actor's current availability and assignments. It is the narrative counterpart to the Redoc reference for team; request and response shapes live there.

Typical flow

  1. GET /v1/projects/{project}/team — fetch the project roster. Each items entry is a ProjectTeamMember carrying actor_id, actor_kind, display_name, availability, and assignments.
  2. Narrow the same call with kind=user or kind=agent when you only need one side of the roster.
  3. Filter by availability or assignment_status to slice on Actor State, or pass q (up to 120 characters) to match against the display name.

The response carries a truncated flag. When it is true, more than 500 rows matched the query — tighten your filters before relying on the result.

Authentication

All operations use the API-wide Bearer scheme described on the API keys page.

Common errors

CodeCauseFix
400A query parameter is malformed — for example, kind outside the user/agent enum or q over 120 characters.Drop or correct the offending parameter and retry.
401API key is missing or invalid.Send a valid Authorization: Bearer <key> header.
403The key cannot view the requested project.Use a key whose org scope includes the project.
404The {project} handle does not resolve.Verify the project handle in the path.

See also

  • Actor State API — the source of availability, assignment_status, and assignments fields surfaced on each team member.
  • Team Redoc reference — full request and response schemas.