> ## 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 Account Suggestions

> Suggest accounts from work email domains your contacts share

# List Account Suggestions

Finds work email domains that several of your contacts share, such as seven contacts at `acme.com`, so you can turn them into accounts. Nothing is created until you [accept a suggestion](/api-reference/accounts/suggestions-accept). See [Accounts](/concepts/accounts).

These are skipped:

* Personal and disposable email providers, such as `gmail.com`, `outlook.com` and `yopmail.com`
* Your own sending domains and their subdomains
* Domains where any contact already belongs to an account, for example through an organization ID sync
* Domains an account already uses as its domain or external ID

Requires the `subscribers:read` scope.

## Request

<ParamField query="minContacts" type="number" default="3">
  Contacts a domain needs to be suggested. Values outside 2 to 1000 are clamped,
  and non-numeric values use the default.
</ParamField>

<ParamField query="limit" type="number" default="25">
  Number of suggestions, largest domains first. Values outside 1 to 100 are
  clamped.
</ParamField>

```bash theme={null}
curl "https://api.sequenzy.com/api/v1/account-suggestions?minContacts=3" \
  -H "Authorization: Bearer API_KEY"
```

## Response

<ResponseField name="suggestions" type="array">
  Suggested accounts, largest first.

  <Expandable title="properties">
    <ResponseField name="domain" type="string">
      The shared work email domain.
    </ResponseField>

    <ResponseField name="name" type="string">
      The name the account gets when you accept it, derived from the domain.
    </ResponseField>

    <ResponseField name="contactCount" type="number">
      Contacts at the domain.
    </ResponseField>

    <ResponseField name="sampleEmails" type="string[]">
      Up to 10 of those contacts' emails, alphabetical, so you can check who
      is behind the suggestion before accepting it.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "suggestions": [
      {
        "domain": "acme.com",
        "name": "Acme",
        "contactCount": 7,
        "sampleEmails": ["ana@acme.com", "ben@acme.com", "chris@acme.com"]
      },
      {
        "domain": "globex.io",
        "name": "Globex",
        "contactCount": 4,
        "sampleEmails": ["dana@globex.io", "eli@globex.io"]
      }
    ]
  }
  ```

  ```json 401 theme={null}
  { "success": false, "error": "Unauthorized" }
  ```

  ```json 403 theme={null}
  { "success": false, "error": "No company selected" }
  ```
</ResponseExample>