---
title: "Check für SMTP Monitor triggern"
description: "Startet einen sofortigen Check von allen zulässigen Monitoring-Standorten."
---

`POST /api/smtp-monitors/:smtpMonitorPublicId/trigger-check`

## Authentifizierung

Erfordert eine gültige Session und Schreibrechte.

- Header: `Authorization: Bearer <token>`

## Parameter

- `smtpMonitorPublicId` (Pfad, erforderlich): Öffentliche UUID des SMTP Monitors.

## cURL

```bash
curl -X POST "https://YOUR_DOMAIN/api/smtp-monitors/33333333-3333-4333-8333-333333333333/trigger-check" \
  -H "Authorization: Bearer $TOKEN"
```

## Response

```json
{
  "success": true,
  "message": "Checks triggered successfully",
  "smtpMonitorId": 200,
  "locationCodes": ["de-nbg", "fi-hel"],
  "queueNames": ["smtp-monitor-checks-de-nbg", "smtp-monitor-checks-fi-hel"]
}
```

## Errors

- `400` SMTP Monitor Public ID (UUID) erforderlich
- `401` Unauthorized
- `403` Forbidden
- `404` Not found
- `500` Failed to trigger check (die Status-Message kann z. B. "No active monitoring locations available" enthalten)