The Orb event page has been updated to allow users to access events sent to Orb within the past 90 days. 

Events on the page can be filtered using the new updated timepicker or by filtering event properties using the Event filter button. More advanced filtering is available through SQL.

Clicking on Download .CSV will apply the current filters and download all events to a CSV file. 

Orb's data exports feature now supports daily revenue broken down by line item through the Daily Line Item Revenue resource.

For customers with data exports included in your plan, this resource will automatically be included in the list of resources being exporter to your data destination.

This resource is a powerful way to understand and track daily quantities and associated costs for invoice line items for both past and current invoices.

This information can be used to power use cases like: daily revenue recognition workflows and running pricing analyses and exercises.

For more information about this resource, please check out our documentation. If you'd like to learn more about the data exports product generally, please feel free to look through our docs or reach out to the Orb team.

Orb now supports returning precomputed responses on the subscription costs, customer costs, and subscription usage endpoints as an opt-in feature through the `Orb-Cache-Control` header.

By default, these endpoints will query the latest events for the resource and execute a live query. For large time ranges, event sets, or many metrics, this can take a few seconds. However, Orb also periodically recomputes usage totals for each customer asynchronously as events are ingested and can now directly serve this data if requested without performing the live query.

Note that cached data is not guaranteed to be entirely fresh, and is meant to serve use cases like an initial load where performance on the critical path is important. In the response, Orb returns a timestamp, which represents the latest time the results are guaranteed to capture. This timestamp can be used to display the freshness to the user, or for your system to decide whether re-querying the endpoint for the latest data is required.

In order to request cached data on these supported endpoints, see this docs page for a more detailed explanation of request and response semantics.

Orb now supports configuring alerts programmatically through our API, enhancing your ability to monitor customer spending and usage with greater control and flexibility at scale. 

Alerts trigger webhooks when credit balances, costs, or usage thresholds are exceeded for customers or subscriptions. These alerts can be used to notify internal teams of anomalous activity, power an overage notification workflow to customers, or prevent excessive use of a product feature.

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. 

The update subscription API endpoint allows you to make updates to the terms of an existing customer subscriptions. This added functionality allows you to programmatically update a specific subscription as your customer’s needs evolve.

This endpoint can be used to update:

• Metadata: individual keys can be removed by setting the value to null, and the entire metadata mapping can be cleared by setting metadata to null.
• Default invoice memo: update the memo on this subscription's invoices. If not provided, it is determined by the plan configuration.
• Auto collection: update whether issued invoices for this subscription will automatically be charged with the saved payment method on the due date.
• Net terms: update when the subscription’s invoices are due from after they are issued.
• Invoicing threshold: update the threshold at which an invoice will be issued for the subscription.

Learn more about this endpoint in the Orb docs.

In the Orb API, you can now configure credit ledger entries so they're granted after an invoice payment is successful. You can do this by setting invoice_settings.require_successful_payment as true when you create a ledger entry. The block will have status="pending_payment" in the /customers/<id>/credits response.

This behavior is supported for ad-hoc credits or automatic top-up credits. If your customer has a credit block that is waiting on a payment, you will see it in the Orb web app in the "Credit block details" section on their customer page. The block will have "pending payment" noted in the current balance column.

In the change plan flow, you can now associate a discount, minimum spend, or maximum spend to a specific price on customer's subscription. You may use this flow if a customer is upgrading or downgrading their subscription to a new plan and you'd like to customize their discount given the specific contract details. To do so, start a plan change from the customer's page in Orb, select a new Plan in Price Settings, and then select "Override" to customize the minimum spend, maximum spend, or discount for a specific price. 

Orb now supports the ability to export accounting sync records to help audit and track records and their various statuses as you set up your accounting system integration. Navigate to the Accounting tab under Settings to check it out!

For more information about this feature and Orb's accounting system integration solution, please check out our docs!