---
title: "Request a service-notice review"
url: https://docs.gleap.ai/en/reference/rest-api/request-service-notice-review
method: POST
path: "/engagement/emails/{engagementEmailId}/service-notice-review"
api: "API Reference"
tag: "Engagement Email"
operationId: "RequestServiceNoticeReview"
updatedAt: "2026-11-02T14:15:01.125Z"
language: en
---

# Request a service-notice review

`POST https://api.gleap.io/v3/engagement/emails/{engagementEmailId}/service-notice-review`

Ask a Gleap teammate to review an email whose service-notice check failed or could not run. Only possible while the latest check of the current content is `fail` or `unavailable`. Approval never sends the email: publish it again afterwards.

## Authorization

- `Authorization` (header, required): `Bearer <token>`

## Path parameters

- `engagementEmailId` (string, required)

## Headers

- `project` (string, required)

## Request body (`application/json`, required)

- `note` (string)

## Example request

```bash
curl --request POST \
  --url 'https://api.gleap.io/v3/engagement/emails/{engagementEmailId}/service-notice-review' \
  --header 'Authorization: Bearer <token>' \
  --header 'project: <project>' \
  --header 'Content-Type: application/json' \
  --data '{
  "note": "<note>"
}'
```

## Responses

### 200 (`application/json`)

Ok

- `reviewTicketId` (string, required)
- `verdict` (enum<string>, required): One of: `pending_review`.

```json
{
  "reviewTicketId": "string",
  "verdict": "pending_review"
}
```
