> ## Documentation Index
> Fetch the complete documentation index at: https://loops.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a transactional group

> Retrieve a single transactional group by ID, including its name, description, and metadata, to inspect how transactional emails are organized.

## Request

### Path parameters

<ParamField path="id" type="string" required>
  The ID of the transactional group.
</ParamField>

## Response

### Success

<ResponseField name="id" type="string" required>
  The transactional group ID.
</ResponseField>

<ResponseField name="name" type="string" required>
  The group name.
</ResponseField>

<ResponseField name="description" type="string" required>
  The group description.
</ResponseField>

<ResponseField name="createdAt" type="string" required>
  ISO 8601 timestamp for when the group was created.
</ResponseField>

<ResponseField name="updatedAt" type="string" required>
  ISO 8601 timestamp for when the group was last updated.
</ResponseField>

### Error

A `400 Bad Request` is returned if `id` is invalid.

A `404 Not Found` is returned if the transactional group does not exist.

If the API key is invalid (or content API is not enabled for your team), a
`401 Unauthorized` is returned.

<ResponseField name="message" type="string" required>
  An error message describing what went wrong.
</ResponseField>

<ResponseExample>
  ```json Response theme={"dark"}
  {
    "id": "tgrp_01hxyz",
    "name": "Account emails",
    "description": "Password resets and verification emails",
    "createdAt": "2026-03-28T15:00:00.000Z",
    "updatedAt": "2026-03-28T15:00:00.000Z"
  }
  ```

  ```json Error response theme={"dark"}
  {
    "message": "Transactional group not found."
  }
  ```
</ResponseExample>