Orb's API now supports adding, removing, and replacing prices when creating a new subscription, or changing the plan for an existing subscription (See: Subscription Price Overrides). This is useful when a new customer has negotiated one or more different prices for a specific plan than the plan's default prices.
For information on how to use this feature, see the API specification:
You can now set a customer’s tax exemption status - tax exempt or not tax exempt directly from the Create Customer or the Update Customer API endpoints. This feature enables smoother integrations and more automated workflows for managing tax compliance. You could use this to: exclude tax collection for customers in specific countries, mark tax-exempt organizations like nonprofits or government entities as tax-exempt in Orb upon creation, or manage tax externally for a specific subset of customers.
More information about Orb's supported tax providers can be found here.
Orb Invoicing now supports the ability to send invoice emails from your own domain. This allows you to fully control the domain and sender of all invoice emails, helping to build confidence when sending invoices to your customers. Learn more here.
For customers with custom email domain support included in your plan, please reach out to your support representative to configure the feature.
There is a new view for a customer's subscription. The page displays metadata, pricing configuration, and activity history specific to a subscription.
Browse to the desired subscription on the customer page, open the overflow menu and click on 'View Details' to see the subscription details.
Orb now allows you to anchor your billing cycles to a custom date. Previously, you were able to specify the day of the month on which billing cycles were anchored. Now, you're able to specify a full date.
For example, a quarterly subscription anchored on March 16, 2024 with a start date of October 10, 2023 and an end date of March 16, 2024 would have the following billing periods: October 10, 2023 - December 16, 2023, December 16, 2023 - March 16, 2024.
Orb now supports specifying a custom billing cadence or one-time service period. Previously, prices could only recur monthly, quarterly, semi-annually, or annually. Now you're able to specify a custom duration in days or months. You can also now specify a custom service period duration for one-time prices, which determines the duration of the line item.
Orb's API now supports the dry running of requests. Dry running API requests allows you to validate the correctness of a request without making any actual changes to the system. This feature is particularly useful for ensuring that the request does not contain any errors and for previewing the potential response of a mutation before committing it.
Dry-running a request is as simple as including a “Dry-Run” header with a value of “True”, as shown below:
curl --request POST \ --url https://api.withorb.com/v1/subscriptions \ --header 'Dry-Run: True' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer null' \ --header 'Content-Type: application/json'
More information can be found in our documentation.
Orb now allows adding and removing prices during subscription creation and plan change. Previously, plan overrides only allowed prices to be modified. This allows the creation of a wide variety of custom plans using a small number of template plans, without having to construct the new plans from scratch. It also makes it easy to create add-ons to existing plans and subscriptions.
See the docs here: Subscription price overrides
We have introduced a new API endpoint, Update Alert, that allows you to update the thresholds of an existing alert. This functionality mirrors our UI's existing edit alert flow for credit balance, usage, and cost alerts.
To learn more about Orb's alerting features, read more in our documentation.
Orb's backfill feature allows you to amend or replace events in a given time frame. This can be useful in cases where revising events is necessary, such as in the case of incorrect event reporting.
Backfills now support filtering across time ranges and with computed properties, which enables the expressiveness of SQL when replacing events. Using the `deprecation_filter` field requires `replace_existing_events` to be true and the filter must be an expression that is coercible to a boolean - for more information, see the docs here.