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 now sends two new webhook events when your plans change:

• plan.created is sent when a plan is created as active or a draft plan is published. Saving a plan as a draft doesn't send an event.
• plan.edited is sent when a plan's name, description, external_plan_id or metadata changes through the API or the dashboard, and when a plan is archived or unarchived. The payload includes the full plan plus previous_attributes with the prior values of the changed fields.

We also shipped a few dashboard improvements:

• Search the coupons list by redemption code.
• Type to filter more dropdowns, including the item dropdown in the credit ledger.
• Leading and trailing whitespace is now trimmed when you paste into a field. Previously, a pasted external ID could carry a stray space and fail to match.

Learn more about webhook events 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.

When you create or edit a collections automation schedule, each step now has a Developer options section. Use it to label the step's webhook and to preview the payload it sends.

• Custom webhook labels: the label you set is sent as properties.label on the invoice.automation_schedule_step_executed event. Your systems can route each step's webhook, for example to a Slack notification, without mapping step IDs.
• Sample payloads: click View sample payload to see and copy an example event for that step, so you can build and test your webhook handler before the schedule runs.

Collections automations are available on Enterprise plans.

Learn more about collections automations in our docs.

Know when a backfill finishes

Two new webhook events, backfill.reflected and backfill.reverted, fire when a backfill's changes have been reflected or when it has been fully reverted. You no longer need to poll for backfill status. Kick off downstream processing or review the results as soon as the backfill is done. Learn more in our webhooks docs.

Control invoice auto-issuance per subscription

You can now set auto_issuance on a subscription when you create it, update it, or schedule a plan change. A subscription without its own setting inherits the customer-level setting, then your account default. Existing subscriptions keep issuing invoices exactly as they do today.

See where every credit block came from

Credit block responses now include credit_block_source (allocation, top-up, commitment, or manual). Blocks funded by a credit allocation also include that allocation's details. This makes it easier to reconcile balances and explain to your customers where their credits came from.

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.

You can now configure Orb to send a webhook whenever a customer is edited. This makes it easier to keep data in sync between Orb and your production systems. Check out our docs for more information!