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 Usage API

[Usage events](https://docs.metronome.com/connecting-metronome/send-usage-data/) are the basis for billable metrics. Use these endpoints to send usage events to Metronome and retrieve aggregated event data.

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

Tagged areas include Usage. 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 19 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 19 schemas 1 GET5 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 Usage 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 — 1 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Usage 6

[Usage events](https://docs.metronome.com/connecting-metronome/send-usage-data/) are the basis for billable metrics. Use these endpoints to send usage events to Metronome and retr…

POST
/v1/ingest
Ingest events
ingest-v1 body → 200
POST
/v1/usage/seats
Get seats usage data
getSeatsUsage-v1 2 params body → 200
POST
/v1/usage/groups
Get usage data with paginated groupings
getPagedUsage-v1 2 params body → 200
POST
/v1/usage
Get batched usage data
getUsageBatch-v1 1 param body → 200
POST
/v1/events/search
Search events
searchEvents-v1 body → 200
GET
/v1/customers/{customer_id}/purchasedSeats
Get purchased seats
getPurchasedSeats-v1 1 param → 200404

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are BillableMetricBase (13 properties), PagedUsageQueryPayload (9 properties), SeatsUsageQueryPayload (7 properties), UsageBatchAggregate (7 properties). Each schema is shown below with its type and property counts.

CustomField
object
Custom fields to be added eg. { "key1": "value1", "key2": "value2" }
BillableMetricBase
object
13 properties 2 required
GroupKey
array
Group key to group usage by. Supports both simple (single key) and compound (multiple keys) group keys. For simple group keys, provide a single key e.g. ["regi…
GroupFilter
object
Object mapping group keys to arrays of values to filter on. Only usage matching these filter values will be returned. Keys must be present in groupkey. Omit a…
PropertyFilter
object
4 properties 1 required
AggregationKey
string
A key that specifies which property of the event is used to aggregate data. This key must be one of the property filter names and is not applicable when the ag…
BillableMetricForEventsSearch
PagedUsageQueryPayload
object
9 properties 3 required
GroupKeysArray
array
Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.
Event
object
5 properties 4 required
SeatsUsageAggregate
object
3 properties 3 required
PropertyFiltersArray
array
A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the bill…
Error
object
1 property 1 required
SeatsUsageQueryPayload
object
7 properties 4 required
UsageBatchQueryPayload
object
5 properties 3 required
PagedUsageAggregate
object
6 properties 5 required
EventTypeFilter
object
An optional filtering rule to match the 'eventtype' property of an event.
2 properties
AggregationTypeForEventsSearch
string
Specifies the type of aggregation performed on matching events. Includes "customsql" for events search endpoint responses.
UsageBatchAggregate
object
7 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

metronome-usage-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 Notifications API
Metronome Packages API
Metronome Payments API
Where this information came from

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