Search teams

Purpose

Performs a filtered search over teams using a POST request. Use this endpoint for batch lookups by IDs, names, or handles when query string filters are insufficient.

Request Format

Supports two formats. Format is auto-detected by the presence of filter or search keys.

New format (recommended): Uses structured filter and search objects. Legacy format (deprecated): Uses flat arrays directly under data.

Key Features

  • filter.id: Filter by team UUIDs (OR logic, max 100)
  • filter.fields.name: Filter by team name, case-insensitive (single string or array, OR logic)
  • filter.fields.handle: Filter by team handle, case-insensitive (single string or array, OR logic)
  • search.query: Full-text search on team name and handle (case-insensitive partial match)
  • Returns the same response format as GET /v2/teams

Filter Logic

  • Multiple values within a single filter use OR logic (e.g., filter.fields.name: ["A", "B"] returns teams named A or B)
  • Different filter types and search use AND logic (e.g., filter AND search = intersection)
  • Empty request returns all teams (same as GET /v2/teams)

Important Notes

  • Each filter array accepts at most 100 items; exceeding this returns a 400 error
  • Pagination uses cursor-based navigation via pageCursor query parameter
Query Params
string

Cursor for pagination.

Body Params
data
object

Search data that accepts both new structured format and legacy flat format. If filter or search is present, the new format is used. Otherwise, the legacy flat format is assumed.

Responses

Language
Credentials
Bearer
JWT
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json