New webhook endpoints now use standard payloads by default. Standard payloads include each object's own fields and references to related objects, but leave out invoice line items and subscription price intervals, so they're smaller and faster to build and deliver. When you need the full object, fetch it from the API after the webhook arrives.

• Choose a payload style, Standard or Expanded, when you create an endpoint in Developers > Webhooks.
• Switch an existing expanded endpoint to standard payloads at any time.
• Every webhook now has typed, autogenerated reference docs for both payload styles.

Note that existing endpoints keep receiving expanded payloads until you change them.

Learn more about webhooks in our docs.

Orb MCP (Model Context Protocol) is not available in Early Access, so your AI agents can connect directly to your Orb account and work with your billing data.

Learn more about setting up the MCP server in our docs.

You can now create and manage webhook endpoints through the Orb API, so you can set up and maintain webhook delivery as code instead of configuring each endpoint by hand.

• Create an endpoint with POST /webhook_endpoints, setting its url, the enabled_event_types it receives (all events if omitted), and its payload_style (standard or expanded).
• List, retrieve, update and delete endpoints, or pause and resume delivery with the disable and enable endpoints.

Note that the signing secret is returned only when you create an endpoint, so store it then. Each account can have up to 20 webhook endpoints by default.

Learn more about managing webhook endpoints in our docs.

We’re excited to introduce a new webhook event: customer.balance_transaction_created. This webhook notifies your systems whenever a balance transaction is created for a customer, for example, when the balance is added via a refund credit note or deducted during invoice issuance.

To start using this webhook, configure your webhook endpoints in the Orb dashboard and ensure your systems are set up to handle the customer.balance_transaction_created event.

For more details, refer to our webhook documentation.

We’re excited to announce the launch of our officially supported Ruby SDK! You can integrate seamlessly with Orb in your Ruby projects using the orb-billing gem, available on RubyGems.org.

To get started, add this line to your Gemfile:

gem 'orb-billing', '~> 0.1.3'

Or install it directly with:

gem install orb-billing

Ruby now joins our growing SDK family alongside Python, TypeScript, Go, Java, and Kotlin, making it even easier to integrate Orb no matter your stack.

Do you have a language you’d like us to support next? Let us know - we’re all ears!

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.

The evaluate price API endpoint allows you to leverage multiple SQL expressions in order to dynamically query your data, just as you would use SQL expressions in constructing your metric. The set of filter and grouping expressions need not be configured up-front or known to Orb to pre-aggregate; instead, you’re able to perform these actions on-demand as they become necessary. Because SQL expressions are supported (as opposed to more basic support for event properties), you can use conditional statements and other logical operators.

This endpoint could be used to:

• View usage for your compute metric broken down by cluster_name, where a user may have hundreds of clusters active in a given time period.
• Build an interactive explorer in your application to view hourly data over a day time range, rather than the default daily views available through Orb’s subscription usage and cost APIs.
• Provide a view into end customer usage by api_key prefix, allowing users to understand the source of API requests.

Learn more about this endpoint in the Orb docs. Happy query-ing! 

Starting today, SDKs for Orb are available in Python (orb-billing on PyPI), Node.js/Typescript (orb-billing on NPM), and Go (github.com/orbcorp/orb-go). We’re pretty excited about the ergonomic wins these SDKs bring when it comes to integrating with Orb. They offer a wide range of benefits including autocomplete, static checking, retries, idempotency support, and more!

Additionally, if an Orb SDK isn’t available in your language of choice, our OpenAPI spec can help you get up and running with one quickly!