Linking Metronome as a source

The companies or accounts you bill. Usage events, contracts and invoices all hang off a customer. Only active customers are synced; Metronome's list endpoint returns archived customers only as a separate, exclusive result set.

Invoices issued to a customer, with their line items. Fetched per customer; Metronome has no account-wide invoice list endpoint.

Contracts define what a customer is charged: the rate card in force, plus its commits, credits, overrides, discounts and scheduled charges. Fetched per customer from the v2 endpoint.

Products are the billable things a rate card prices: usage, subscription, composite, fixed, or professional-services. Includes archived products.

Rate cards hold the prices charged for products. Contracts reference a rate card rather than carrying prices themselves. The rates on a card are fetched separately and are not part of this table.

Packages are reusable contract templates: a rate card plus the commits, credits, overrides and charges a new contract should start with. Includes archived packages.

Billable metrics turn raw usage events into the quantities products charge for, by filtering events and aggregating a property. Includes archived metrics.

The units prices and balances are denominated in: fiat currencies plus any custom credit types your account defines.

Plans are Metronome's original way to price a customer. This table lists the plans defined in your account, with each plan's name, description, and custom fields. Metronome has deprecated plans in favor of contracts. It holds plan definitions only, not which customer is on which plan, so it does not by itself link a plan to a customer or an invoice.

Aggregated usage per customer and billable metric, across every customer in the account. Each row is one lifetime total for a customer and metric pair. To see how much a customer used inside a period, sync the usage_daily or usage_hourly table instead.

Usage per customer, billable metric and day, across every customer in the account. Use it to track what a customer consumed inside a billing period, or to chart usage over time. The first sync covers the last 365 days, and later syncs add each new day. The day in progress is included, and every sync updates it. Metronome accepts usage events backdated up to 34 days, so to keep earlier days up to date as well, set a lookback window in the table's sync settings.

Usage per customer, billable metric and hour, across every customer in the account. It answers the same questions as the daily table at a finer grain, which helps when you need to see spikes inside a day. It holds 24 times as many rows, so the first sync covers the last 30 days rather than a year. The hour in progress is included, and every sync updates it. Metronome accepts usage events backdated up to 34 days, so to keep earlier hours up to date as well, set a lookback window in the table's sync settings.

One row per change made through the Metronome app or API: who did it, to what, and whether it succeeded. It is the only Metronome list endpoint with a server-side time filter, so each sync reads only the entries recorded since the last one.