You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Best practice for managing REST API versions in Oracle CPQ BML scripts

edited Jun 18, 2026 2:59PM in Configure Price Quote 1 comment

Hi everyone,

I'm currently working on several BML scripts that interact with the Oracle CPQ REST API (e.g., /rest/v18/...). I've noticed that I cannot use a generic /rest/latest/ path, which means I currently have to hardcode the version directly into my URL strings.

I’m looking for the community's recommended approach to make these scripts more maintainable:

  • Is it considered best practice to store the API version in a Data Table to avoid hardcoding it in every single script?
  • How do you handle API version upgrades across your environments (DEV/UAT/PROD) to ensure minimal downtime and testing effort?
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!