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

OpenMeter Notifications API

Notification channels, rules, and events for usage-driven alerts.

OpenMeter Notifications API is one of 10 APIs that OpenMeter 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 an API reference.

This API exposes 5 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://openmeter.cloud, http://localhost:8888.

5 operations 3 paths 3 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://openmeter.cloud/api/v1
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • BearerAuth — OpenMeter Cloud API token supplied as a Bearer token.

Paths & Operations 5

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

Notifications 5

Notification channels, rules, and events for usage-driven alerts.

GET
/api/v1/notification/channels
List notification channels
listNotificationChannels → 200
POST
/api/v1/notification/channels
Create a notification channel
createNotificationChannel body → 201
GET
/api/v1/notification/rules
List notification rules
listNotificationRules → 200
POST
/api/v1/notification/rules
Create a notification rule
createNotificationRule body → 201
GET
/api/v1/notification/events
List notification events
listNotificationEvents → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are NotificationRule (6 properties), NotificationChannel (6 properties), NotificationEvent (5 properties). Each schema is shown below with its type and property counts.

NotificationEvent
object
5 properties
NotificationChannel
object
6 properties 2 required
NotificationRule
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmeter-notifications-api-openapi.yml Raw ↑

Other APIs OpenMeter publishes across the network.

OpenMeter Billing API
OpenMeter Customers API
OpenMeter Entitlements API
OpenMeter Events API
OpenMeter Features API
OpenMeter Grants API
OpenMeter Meters API
OpenMeter Plans API
OpenMeter Subjects API
Where this information came from

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