Team ID (tem_...) whose threads should be listed.
Request body.
Optionalskip_welcome_message?: booleanWhen true, suppresses the automatic welcome message that is otherwise sent into the thread on creation. Defaults to false.
Attributes for the new thread. See ThreadCreateParams for available fields.
The newly created thread.
List threads for a team
Returns all threads owned by the specified team that the authenticated caller
has permission to view. The caller must have access to the team; requests
without team access are rejected with 404.
Threads are returned in a single data array, ordered with the team's
default thread first, then by most recent activity (newest first). Each
thread carries a last_activity timestamp — the most recent message's
creation time, falling back to the thread's own creation time. Use the
team-scoped thread endpoints to create, update, or delete individual
threads.
Team ID (tem_...) whose threads should be listed.
Optionalparams: { tags?: string[] }Query parameters.
Optionaltags?: string[]Optional: only return threads tagged with at least one of these tags (OR-match). Repeated query params, e.g. ?tags[]=blocked&tags[]=needs-review.
Successful response
Get threads-created count for a team
Returns how many network-public team threads were created in the UTC-day
window. Counts come from realtime SQL aggregation over append-only
network_activity_events (thread.created rows co-committed with create):
team- or restricted-visibility threads (plus legacy open-team rows), never
private or mirror. Every Network member sees the same number. Hard-delete
co-commits a separate thread.deleted transition event and does not remove
create events (metric is "created", not "still present"). Visibility flips
after insert are ignored in v1.
Any authenticated team member may read this count-only Network summary.
Requests from callers without team access return 404 so team existence is
not disclosed.
Team ID (tem_...) whose threads should be listed.
Optionalparams: { days?: number }Query parameters.
Optionaldays?: numberUTC-day window. One of 7, 30, 90, or 365; defaults to 30.
Successful response
Create a thread for a team Creates a new thread owned by the specified team. The authenticated caller must have access to the team; requests from callers without team access are rejected with 404. If a
profile_pictureis provided in the thread params, it must be base64-encoded image data. The image is uploaded and associated with the thread before creation completes. Omitprofile_pictureto skip this step. By default the platform sends an automatic welcome message into the new thread. Passskip_welcome_message: trueto suppress this behavior, for example when creating threads programmatically in bulk or seeding test data.