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

# List Brand Requests

> Your requests to add brands, like competitors, to the email gallery

List your requests to add brands, usually competitors, to the [Sequenzy email gallery](https://sequenzy.com/email-examples), newest first, with where each one stands. These are the requests from **Suggest a brand** in the dashboard's gallery picker. Requests are private to your company.

Each request moves from `requested` to `collecting` once the brand is added to the gallery, then to `available` once its emails are in. Then `brand.url` links to them, and [List Email References](/api-reference/references/list) can return them.

Requires the `templates:read` scope.

```bash theme={null}
curl "https://api.sequenzy.com/api/v1/gallery/brand-requests" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response

<ResponseField name="requests" type="object[]">
  Your requests, newest first.

  <Expandable title="properties">
    <ResponseField name="id" type="string">Request ID.</ResponseField>
    <ResponseField name="domain" type="string">The brand's registrable domain, such as `competitor.com`.</ResponseField>
    <ResponseField name="note" type="string | null">What you asked to see from the brand.</ResponseField>
    <ResponseField name="status" type="string">`requested` (not in the gallery yet), `collecting` (added, emails being collected), `available` (its emails are in the gallery) or `declined`.</ResponseField>
    <ResponseField name="declineReason" type="string | null">Why the brand won't be added, when declined.</ResponseField>
    <ResponseField name="requestedAt" type="string">When you asked (ISO 8601).</ResponseField>
    <ResponseField name="brand" type="object | null">Once `available`: the gallery brand's `name`, `slug` and `url`.</ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="limit" type="integer">
  How many requests your company can keep, declined ones included.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "requests": [
      {
        "id": "req_8fk2",
        "domain": "linear.app",
        "note": "Their onboarding emails",
        "status": "available",
        "declineReason": null,
        "requestedAt": "2026-10-01T09:12:00.000Z",
        "brand": {
          "name": "Linear",
          "slug": "linear",
          "url": "https://sequenzy.com/email-examples/brands/linear"
        }
      },
      {
        "id": "req_3jd9",
        "domain": "competitor.com",
        "note": null,
        "status": "requested",
        "declineReason": null,
        "requestedAt": "2026-10-02T15:40:00.000Z",
        "brand": null
      }
    ],
    "limit": 50
  }
  ```

  ```json 401 theme={null}
  {
    "error": "Invalid API key"
  }
  ```

  ```json 403 theme={null}
  {
    "error": "API key is missing required scope: templates:read"
  }
  ```
</ResponseExample>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.