Region Specific API URLs
The process of calling the Rule Solver, Managment API or BI API is the same for region-locked accounts and Global Cloud accounts. The only difference is the endpoint URL.
With the Regional Cloud accounts having to prepend the URL with their respective regional shortcut.
Location | Shortcut | API call URL example |
---|---|---|
![]() | us | https://us.api.decisionrules.io/:PATH |
![]() | eu | https://eu.api.decisionrules.io/:PATH |
![]() | au | https://au.api.decisionrules.io/:PATH |
Let's say you want to solve a rule on an account registered in the
United States. We would follow the instructions in the Rule Solver API article and simply prepend the usual URL with our region's shortcut. In this case 'us', forming the following request:

post
https://us.api.decisionrules.io
/rule/solve/:ruleId/:version
Solve Rule
Let's say you want to update a rule on an account registered in the
EU. We would follow the instructions in the Management API article and simply prepend the usual URL with our region's shortcut. In this case 'eu', forming the following request:

put
https://eu.api.decisionrules.io
/api/rule/:ruleId/:version
Update rule
Let's say you want to get console logs for a rule solve on an account registered in
Australia. We would follow the instructions in the Console Logs API article and simply prepend the usual URL with our region's shortcut. In this case 'au', forming the following request:

get
https://au.api.decisionrules.io
/consoleLogs/:correlationId
Get Console Logs for a solve