Changelog / October 2026
Usage-based billing is here
Charge for what your customers actually use. Usage-based billing lets you attach a meter to any price: API calls, seats, gigabytes or anything else you count. Halyard totals the events, rates them and puts them on the next invoice.
API calls1.44M
Seats38
Storage212 GB
Send events with POST /v2/usage, or let our Stripe sync bring them in. Invoices now show projected usage before the period closes, so nobody is surprised.
8 comments
This is the one we've been waiting for. Does metering work with our existing Stripe price IDs, or do we need to recreate every product?
Existing price IDs work. Halyard maps each meter to a price, so you only add a
meterkey:Nothing changes for customers on flat plans.
Perfect, thanks @maya. Migrating our first plan this afternoon.
We moved two customers over this morning. The invoice preview showing projected usage is a lovely touch.
One request: could the CSV export include the meter name? Finance asked within the hour.
Seconding this. Also, is there a way to backfill usage from before the switch?
This comment was deleted.
Per invoice line, so fractions only round once. The rounding notes have a worked example.
Heads-up for anyone on the API:
GET /v2/usagereturns timestamps in UTC. Our dashboard was a day off until I noticed:Thanks, everyone. Meter names in the CSV export ship next week. Backfill is in beta: reply here and I'll switch it on for your account.