> ## 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.

# Get Email Design System

> Get the visual identity every AI-generated email renders inside

Get the company's effective email design system - the locked visual grammar (kicker style, title alignment, button shape, divider style, density, sanctioned opener treatments) and the composition spine that anchors how AI-generated emails and sequence steps are structured.

The identity is stored as the company's `emailDesignPrompt` design direction text: tokens are parsed from that text, and any token the text does not state is derived deterministically from brand context. While the text is empty or untouched, `isDefault` is `true`. Adjust tokens with [Update Email Design System](/api-reference/email-design-system/update), or edit the text as free prose via `PATCH /companies/:companyId`.

## Request

```bash theme={null}
curl "https://api.sequenzy.com/api/v1/email-design-system" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response fields

<ResponseField name="designSystem.designCode.kickerStyle" type="string">
  How eyebrows above titles render: `chip` (soft badge chips), `letterspaced`
  (uppercase letter-spaced text), or `none`.
</ResponseField>

<ResponseField name="designSystem.designCode.titleAlignment" type="string">
  `left` or `center` alignment for headings and hero content.
</ResponseField>

<ResponseField name="designSystem.designCode.buttonShape" type="string">
  `rounded` rectangles or fully rounded `pill` buttons.
</ResponseField>

<ResponseField name="designSystem.designCode.dividerStyle" type="string">
  `line` (thin dividers between sections) or `space` (whitespace only).
</ResponseField>

<ResponseField name="designSystem.designCode.density" type="string">
  `airy` (generous spacing) or `compact` (tight sections).
</ResponseField>

<ResponseField name="designSystem.designCode.openerTreatments" type="string[]">
  The opener treatments this company's emails may use, primary first. Values:
  `hero-image`, `hero-color`, `header-hero`, `editorial-masthead`,
  `title-led`.
</ResponseField>

<ResponseField name="designSystem.compositionSpine" type="string">
  Which worked-example skeleton anchors generation: `hero-led` (designed
  marketing sections), `editorial` (typography-first), or `product-spec`
  (information-dense).
</ResponseField>

<ResponseField name="designSystem.source" type="string">
  `derived` when every token comes from brand derivation; `custom` when the
  direction text carries the identity.
</ResponseField>

<ResponseField name="directionText" type="string | null">
  The raw design direction text the tokens were parsed from; `null` when the
  company has none yet.
</ResponseField>

<ResponseField name="isDefault" type="boolean">
  True while the identity is purely derived from brand context.
</ResponseField>

## Responses

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "designSystem": {
      "version": 1,
      "designCode": {
        "version": 1,
        "kickerStyle": "letterspaced",
        "titleAlignment": "center",
        "buttonShape": "pill",
        "dividerStyle": "line",
        "density": "airy",
        "openerTreatments": ["editorial-masthead", "hero-color"]
      },
      "compositionSpine": "editorial",
      "source": "derived"
    },
    "directionText": null,
    "isDefault": true
  }
  ```

  ```json 401 theme={null}
  {"success": false, "error": {"code": "UNAUTHORIZED", "message": "Invalid API key"}}
  ```

  ```json 404 theme={null}
  {"success": false, "error": {"code": "NOT_FOUND", "message": "Company not found"}}
  ```
</ResponseExample>