ArchAstro. V1. Teams. Threads
(archastro v0.1.0)
Copy Markdown
TeamThread API resource.
Summary
Functions
@spec create( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.PostApiV1TeamsTeamThreads.Input.t() ) :: {:ok, ArchAstro.Types.Thread.t()} | {:error, ArchAstro.Error.reason()}
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_picture is provided in the thread params, it must be
base64-encoded image data. The image is uploaded and associated with the thread
before creation completes. Omit profile_picture to skip this step.
By default the platform sends an automatic welcome message into the new thread.
Pass skip_welcome_message: true to suppress this behavior, for example when
creating threads programmatically in bulk or seeding test data.
The newly created thread.
@spec list( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.GetApiV1TeamsTeamThreads.Params.t() ) :: {:ok, ArchAstro.Types.Operations.GetApiV1TeamsTeamThreads.Response.t()} | {:error, ArchAstro.Error.reason()}
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.
Successful response