---
title: "List the calling account's active push subscriptions"
method: GET
path: "/api/v1/push/subscriptions"
tags: ["Push"]
---

# List the calling account's active push subscriptions

`GET /api/v1/push/subscriptions`

## Request

- Base URL: `https://api.uptimemonitoring.com`
- URL: `https://api.uptimemonitoring.com/api/v1/push/subscriptions`
- Auth: HTTP bearer

Returns the calling account's active push subscriptions newest
first. The `p256dh` and `auth` secrets are NEVER included in
the response. Returns `[]` (not `null`) when the account has
no subscriptions.

## Response `200`

Subscriptions list.

- PushSubscriptionResponse[]
  - `id` integer
  - `endpoint` string, uri
  - `user_agent` string, nullable
  - `created_at` string, date-time

## Other responses

- `401`: Missing or invalid credentials.
- `403`: Account is currently suspended. On `POST /api/v1/monitors`, and on a `PUT /api/v1/monitors/{monitorID}` that changes `url` or `type` (issue #335), this can also be returned by the per-account port-scan heuristic when the triggering request crossed the port-fan threshold inside the sliding window (10 minutes by default; `SCAN_WINDOW`). A host-fan trip does NOT suspend the account — see the 429 response instead.
- `429`: Per-account dispatcher rate limit exceeded (200 requests/minute). The `Retry-After` header gives the integer seconds until at least one token has refilled. The `X-RateLimit-*` trio reflects the bucket whose rejection produced this response — usually the global 200/min cap; on `POST /api/v1/monitors` a 429 may instead reflect the per-route 20/min creation limit.

---

[API](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api.md) · [All operations](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/revisions/ddcb2a8bc70f?raw)