How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Pepperdata Alarms API

Create, retrieve, revise, and delete metric alarms.

Pepperdata Alarms API is one of 3 APIs that Pepperdata publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Alarms. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against a single base URL, https://dashboard.pepperdata.com/{realm}/api.

7 operations 4 paths 2 schemas 1 DELETE4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://dashboard.pepperdata.com/pepperdata-demonstration/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Pepperdata Alarms API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (PDAPIAuth). By default, every request must be authenticated.

  • PDAPIAuth — API key authentication. Send the header Authorization: PDAPI : . Obtain a key at https://dashboard.pepperdata.com/account/apikeys and click Create API Key. A k…

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Alarms 7

Create, retrieve, revise, and delete metric alarms.

GET
/alarms
List configured alarms
listAlarms → 200401
POST
/alarms
Create an alarm
createAlarm body → 200400401
GET
/alarms/status
List firing alarms
listFiringAlarms → 200401
GET
/alarms/app/{appId}
List alarms for an app/job
listAlarmsByApp 1 param → 200401404
GET
/alarms/{alarmId}
Get an alarm
getAlarm 1 param → 200401404
PUT
/alarms/{alarmId}
Revise an alarm
updateAlarm 1 param body → 200400401404
DELETE
/alarms/{alarmId}
Delete an alarm
deleteAlarm 1 param → 200401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Alarm (8 properties), Threshold (4 properties). Each schema is shown below with its type and property counts.

Threshold
object
Object containing the alarm firing criteria.
4 properties 1 required
Alarm
object
8 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pepperdata-alarms-api-openapi.yml Raw ↑

Other APIs Pepperdata publishes across the network.

Pepperdata Job Details API
Pepperdata Metrics API
Where this information came from

This is an independent, third-party profile of Pepperdata Alarms API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.