Updated the Push Pricing Process to Ensure the “Commit=1” Function Properly.

What's changing? 

We've fixed an issue in the Push Pricing Ingest API where transaction windows weren't closing properly when errors occurred. The API now correctly honors the commit=1 parameter and handles transaction windows as expected, even when request errors are encountered. This update went live in October 2025.

Why this matters: 

Previously, if you made an error in your API request body (like malformed JSON), the transaction window would remain open despite including commit=1 in your request. This created unexpected behavior and required manual intervention to close orphaned transaction windows. The API now handles errors intelligently.

What do you need to do? 

No action is required. Your existing Push Pricing workflows will now behave more predictably when errors occur. If you've implemented workarounds for this issue, you can safely remove them. The API will automatically close transaction windows when appropriate based on the error type and call context.

Reference: 

Full Push Pricing documentation is available HERE.