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

Metronome Notifications API

The Notifications API from Metronome — 6 operation(s) for notifications.

Metronome Notifications API is one of 18 APIs that Metronome publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Notification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 6 operations across 6 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.metronome.com.

6 operations 6 paths 10 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.metronome.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Metronome Notifications API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 POST. Each is listed below with its method, path, parameters, and response codes.

Notifications 6
POST
/v2/notifications/create
Create an offset lifecycle event notification configuration
createNotificationConfig-v2 body → 200400
POST
/v2/notifications/get
Get an offset lifecycle event notification configuration
getNotificationConfig-v2 body → 200400404
POST
/v2/notifications/offset/list
List offset lifecycle event notification configurations
listOffsetNotificationConfigs-v2 body → 200
POST
/v2/notifications/system/list
List system notification event types
listSystemNotificationConfigs-v2 → 200
POST
/v2/notifications/edit
Edit an offset lifecycle event notification configuration
editNotificationConfig-v2 body → 200400
POST
/v2/notifications/archive
Archive an offset lifecycle event notification configuration
archiveNotificationConfig-v2 body → 200400404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are LifecycleEventOffsetNotificationConfig (8 properties), EditNotificationConfigPayload (3 properties), ListOffsetNotificationConfigsPayload (3 properties), LifecycleEventSystemNotificationConfig (3 properties). Each schema is shown below with its type and property counts.

EditNotificationConfigPayload
object
3 properties 1 required
LifecycleEventSystemNotificationConfig
object
3 properties 2 required
LifecycleEventOffsetPolicy
object
2 properties 2 required
ArchiveNotificationConfigPayload
object
1 property 1 required
GetNotificationConfigPayload
object
1 property 1 required
LifecycleEventSystemPolicy
object
1 property 1 required
ListOffsetNotificationConfigsPayload
object
3 properties
LifecycleEventOffsetNotificationConfig
object
8 properties 8 required
UniquenessKey
string
Prevents the creation of duplicates. If a request to create a record is made with a previously used uniqueness key, a new record will not be created and the re…
CreateNotificationConfigPayload
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

metronome-notifications-api-openapi.yml Raw ↑

Other APIs Metronome publishes across the network.

Metronome Alerts API
Metronome Billable Metrics API
Metronome Contracts API
Metronome Credits and commits API
Metronome Custom fields API
Metronome Customers API
Metronome Integrations API
Metronome Invoices API
Metronome Named schedules API
Metronome Packages API
Metronome Payments API
Metronome Products API
Where this information came from

This is an independent, third-party profile of Metronome Notifications 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.