---
title: "Get one account group and its members"
method: GET
path: "/groups/{groupId}"
tags: ["Accounts"]
---

# Get one account group and its members

`GET /groups/{groupId}`

## Request

- Base URL: `https://www.juzpost.com/api/cli/v1`
- URL: `https://www.juzpost.com/api/cli/v1/groups/{groupId}`
- Auth: HTTP bearer

Returns a single channel group with the full list of social account ids in it. A group
belonging to someone else is reported as `404`, never `403`.

## Path parameters

- `groupId` string, uuid, required

## Response `200`

The group and its member account ids.

- Group: A channel group: a named bundle of social accounts you can schedule to by name.
  - `id` string, uuid, required: The group id.
  - `name` string, required: The group's name. This is the value `POST /schedule` accepts in its `group` field, matched exactly.
  - `accountIds` string[], required: Ids of the social accounts in this group, in no guaranteed order.
  - `accountCount` integer, required: How many accounts are in the group. The bulk scheduler rejects groups of more than 10 with a `422`.
  - `createdAt` string, date-time, required: When the group was created.

## Other responses

- `401`: No bearer token was sent, or the token is unknown, revoked or malformed. Run the device login again to obtain a new token.
- `402`: The plan behind this token does not include the capability this operation needs. `error.details.requiredPlan` names the tier that does. This is never a token problem, so do not retry without changing the plan.
- `404`: No such resource. A resource that belongs to someone else is also reported here, so this never confirms whether another tenant's id exists.

---

[API](https://skmtc.dev/juzpost/apis/juzpost-rest-api.md) · [All operations](https://skmtc.dev/juzpost/apis/juzpost-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/juzpost/apis/juzpost-rest-api/revisions/19296da24f95?raw)