---
title: "Get a notification snooze for a user"
method: GET
path: "/v6/notifications/{userId}/snoozes/{snoozeId}"
tags: ["User Notifications"]
---

# Get a notification snooze for a user

`GET /v6/notifications/{userId}/snoozes/{snoozeId}`

Returns the snooze rule identified by `snoozeId` belonging to the Extole portal user identified by `userId`. Returns the tags being snoozed and the expiry timestamp.

## Path parameters

- `userId` string, required
- `snoozeId` string, required

## Response `200`

Notification snooze.

- SnoozeResponse
  - `comment` string, required
  - `expires_at` string, required — [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) or [RFC 9557](https://datatracker.ietf.org/doc/html/rfc9557#section-4) date-time with a numeric [UTC offset](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and an optional [IANA time-zone](https://datatracker.ietf.org/doc/html/rfc9557#section-4) suffix in square brackets. Precision up to milliseconds.
  - `having_exactly_tags` string[], required
  - `snooze_id` string, required

## Other responses

- `400` — User or snooze lookup failed: `user_not_found` if the `userId` does not correspond to a known portal user; `invalid_user_id` if the `userId` is not a valid identifier; `invalid_snooze_id` if the `snoozeId` does not match any snooze rule for that user.
- `401` — Unauthorized
- `402` — Payment Required
- `403` — Forbidden
- `415` — Unsupported Media Type
- `429` — Too Many Requests

---

[API](https://skmtc.net/extole/apis/integration-api-server-to-extole.md) · [All operations](https://skmtc.net/extole/apis/integration-api-server-to-extole/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/extole/integration-api-server-to-extole/versions/c16e62e66755/schema)