You can list invoices with GET /v1/invoices/summary, a lighter version of the invoices list endpoint that responds faster. Each invoice comes back with its invoice-level fields: customer, status, totals, and dates.

To keep responses fast, the summary leaves out:

• Line items
• Minimums and maximums
• Discounts

It takes the same filters as the full list endpoint, including status, customer, and invoice date, due date, and amount ranges.

Use it when you need to page through invoices quickly, such as a billing history view or a status poll, and fetch an individual invoice when you need its line-item detail. For the current period's accruing charges, use /v1/invoices/upcoming.

This endpoint pairs with GET /v1/subscriptions/summary for subscriptions. Learn more about summary lists in our docs.

The default event volume limit in live mode is now 200,000 events per minute, about 300 million events per day, with no setup required. Previously, the default was 10,000 events per minute. If you need more, contact Orb support.

The limit counts events, not requests, so batching is how you use your full volume. Each call to the ingest endpoint (POST /v1/ingest) accepts up to 500 events. Ingestion also has a request rate safeguard, so integrations that send one event per request may hit it before the volume limit.

• Test mode stays at 2,000 events per minute, and trial accounts at 100 events per minute.
• Above about 10,000 events per second, we recommend syncing events through an S3 or GCS bucket for resiliency.

Learn more about rate limits in our docs.

You can now list subscriptions with GET /subscriptions/summary, a lighter version of the subscriptions list endpoint: each subscription comes back with its own fields, and its plan and customer are returned as references rather than full objects.

To keep responses fast, the summary leaves out derived fields such as:

• Price intervals
• Billing periods
• Plan phases

Use it when you need to page through subscriptions quickly and only need their core fields, and fetch an individual subscription when you need its pricing or billing period details.

Learn more about summary lists in our docs.

Over the last two weeks, we made significant performance improvements to the Orb dashboard. In particular, the customer list, the customer detail page, and the invoice list should now load faster. You can expect additional performance improvements in the weeks and months to come.

Orb's customer search feature is now more flexible and broad in its capabilities. You can now search for customers based on a prefix, direct match, or prominent substring across the customer's name, customer ID, external customer ID, and email. 

We've optimized Orb's event ingestion pipeline to make your events visible in Orb faster after initial ingestion. Previously, with high throughput workloads, the most significant contributor to delays was our idempotency deduplication. We've improved our implementation to preserve low ingestion delays even as event throughput increases.

Our product philosophy at Orb has always been to reduce data infrastructure that your team needs to build. We've delivered on that with a truly extensible SQL layer when configuring metrics, so you don't have to maintain that business logic outside of Orb. In many cases, that means you need to send Orb a raw stream of events — if you serve a large customer base or handle a lot of traffic, you should be able to use Orb without any aggregation or transformations up front.

Whereas Orb's ingestion API is meant for services that emit tens of thousands of events a minute, this new functionality is built to support hundreds of thousands of events a second. 

Orb's streaming aggregation functionality requires you to set up an S3 bucket in your account — we handle listening for updates to the bucket (no specific path structure required!), doing the data de-duplication, rollup, and ingesting events directly into your Orb account.

To learn more about what's required for this setup, see the docs on high throughput workloads.