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

# Get Alert Config

Use this API to read the workspace's stored alert settings.

# Endpoint

`POST https://api.velt.dev/v2/memory/alerts/config/get`

# Headers

<ParamField header="x-velt-api-key" type="string" required>
  Your API key.
</ParamField>

<ParamField header="x-velt-auth-token" type="string" required>
  Your [Auth Token](/docs/security/auth-tokens).
</ParamField>

# Body

#### Params

<ParamField body="data" type="object" required>
  No fields required. Send an empty object.
</ParamField>

## **Example Requests**

#### Get the alert config

```JSON theme={null}
{
  "data": {}
}
```

# Response

Only `enabled` is always present. `maxAlertsPerWeek`, `enabledAlertTypes`, and `severityThreshold` appear only after you set them with [Update Alert Config](/docs/api-reference/rest-apis/v2/memory/alerts/config/update). A workspace that has never updated the config gets `{ "enabled": true }`. `enabledAlertTypes` holds alert types: `anomaly`, `configuration_drift`, `emerging_standard`, or `standards_drift`.

These values are stored and returned as sent. They are not applied to alert generation today. Alerts are capped at 3 per rolling 7 days per workspace.

#### Success Response

```JSON theme={null}
{
  "result": {
    "enabled": true,
    "maxAlertsPerWeek": 5,
    "enabledAlertTypes": ["anomaly", "standards_drift"],
    "severityThreshold": "medium"
  }
}
```

#### Failure Response

```JSON theme={null}
{
  "error": {
    "message": "ERROR_MESSAGE",
    "status": "INVALID_ARGUMENT"
  }
}
```

<ResponseExample>
  ```js theme={null}
  {
    "result": {
      "enabled": true,
      "maxAlertsPerWeek": 5,
      "enabledAlertTypes": ["anomaly", "standards_drift"],
      "severityThreshold": "medium"
    }
  }
  ```
</ResponseExample>