Are Velo API consistent and Stable?

Talking about consistency:

I need to update the plan when any item is purchased from the Pricing Plans…

I see that API Docs suggests to use the following code in events.js file as a event callback=>

export function wixPricingPlans_onPlanPurchased(event) {
  // ... code here
}

However it’s never being called

Then I came across another section in the document that says to use wixPricingPlansBackend_onPlanPurchased instead… I tried to use it as well but — it neither works…

Talking about Stability:

The question also arises if these API are stable??? And If I start using them in my production application would they work consistently and behave stable?

The APIs, for the most part, are stable. However, I’ve had a few scenarios where Wix makes updates that “breaks” an API for a few days - one of which involved the pricingPlans API.

How often does this happen? And how to rely on stability then?

“pricingPlans API” is a critical area – if any other functionality is impacted, it’s still Okay – but If the payment of customer is impacted… how can this be even used???

There has to be a way to stick to the stable version… and I upgrade only on demand — so that I know and thoroughly test it before releasing it to my customers

In 95% of all time, Wix-Apis are stable.
Only if it comes to —> UPDATING-PROCESSES <— sometimes you will get some troubles. But normaly after 1-2weeks most of BUGS are eleminated again.

Yes, not the best way to provide users new UPDATES including new APIs, but at the end ----> We all are programmer → and we all know how fast BUGS can be coded into a working code.

Normaly i would say → !!! NEVER TOUCH A RUNNING (WORKING) SYSTEM !!!
But in this case this sentence do not work :grin:

The APIs were down for 2 weeks in that 95%… many API do NOT work in preview mode and has to be deployed… A BIG matter of concern