The API doesn't currently expose an endpoint to fetch existing routing rules. Developers who want to read, modify, and reapply rules programmatically have to make changes manually in the UI, which doesn't support automation or version-controlled rule management.
Requested behavior: Add a GET endpoint that returns the full definition of a routing rule, including conditions, actions, and metadata, so developers can programmatically fetch, inspect, and modify rules without relying on the UI.
Why it matters: Without read access to rules via API, any automated rule management workflow is incomplete. Teams managing large rule sets or building CI/CD-style configuration pipelines need to be able to read rules the same way they write them.