We will be only keeping the webhook log entries for 30 days.

Originally we had the retry logic attempts match the errorThreshold attribute on Webhooks, but we have now capped that at 3 total attempts. However, if the errorThreshold field is set to lower than 3 that will be the max retry attempt. All other retry and email logic remains the same. See updated docs: Webhook docs

The GET /v1/subscriptions/{subscriptionId} endpoint now includes the new vendorSubscriptionId field. For Microsoft products, this field directly provides the corresponding Microsoft Graph API subscription ID. This enhancement significantly simplifies the process of reconciling subscriptions between Pax8 and Microsoft, enabling more streamlined automation and integration.

Provision requests now support volume commitment terms alongside time only based commitments. Volume commitments allow minimum and maximum volume requirements with flexible units of measure.

There was a mistake on the documents for refresh token lifetime limit. The docs stated this was alive for 1 year, which is not the case. The real lifecycle is 90 days for a refresh token before the user is required to re-authorize the app.

The /v1/products endpoint now supports a powerful new search parameter that enables querying across multiple product attributes, including product name, description, and ID. This enhancement provides more flexible and comprehensive search functionality for your product catalog.

The Product API now includes the long description for a product under the description field.

The Provisioning API now has a new request type of Renewal. The newRenewal type represents a request to confirm the continuation of an existing subscription for another commitment term.

Before this update, the Usage API would always react to multiple batches of usage sent on the same day in one way: it would overwrite old batches with the new batch. Now this behavior can be changed. Vendors can now send a new parameter called overwriteSameDayUsage when posting usage, and if set to false, usage batches will accumulate instead of overwrite one another. Learn more here

The usage api has a new endpoint that accepts a new type called Aggregate Usage Line. Aggregate Usage Lines have a required partnerAggregateQuantity field, which will be used in lieu of the quantity when calculating the partner price for the usage line. More here.