Overview

Retrieve a paginated list of alerts generated for the specified subscription ID. Each alert includes: - `alertId`: unique identifier for the alert - `createdAt`: timestamp of when the alert was generated Results are sorted in descending order of `createdAt` (most recent first).

Quickstart

Follow these two steps to make a request and recognize a successful response.

curl --request GET \
  --url https://uapi.demandbase.com/data/b2b/v1/subscriptions/287ea0c8-99de-4f0c-addc-097f78b48ba6/alerts?page=1&perPage=10 \
  --header "Authorization: Bearer $DB_API_KEY" \
  --header "Accept: application/json"

{
  "alerts": [
    {
      "alertId": 3,
      "createdAt": "2025-05-23T15:25:56.202+05:30"
    }
  ],
  "pageNo": 1,
  "pageSize": 2,
  "totalCount": 1,
  "totalPages": 1
}

Request anatomy

Build the request from the method, path, parameters, and payload described below.

Parameters

Request body

This endpoint does not define a JSON request body.

Response anatomy

The endpoint returns 200 for the documented success case. Subscription alert details list fetched successfully

The response schema does not enumerate fields; inspect the example response and status code.

Rules

• Use GET with the path /subscriptions/{subscriptionId}/alerts.
• Required inputs: subscriptionId.
• Authenticate every request with a valid Demandbase access token.
• This endpoint does not require a JSON request body.

Filters

The published schema exposes the following endpoint inputs. Use the location column to place each value correctly.

Errors

Handle non-success responses explicitly so your integration can report actionable failures.

Next steps

Back to top