Skip to main content
Solved

eep-linking from RingCX data to a specific call in RingSense — what ID do I need?

  • April 28, 2026
  • 1 reply
  • 87 views

Hi all,

We pull a scheduled Interaction Details report from RingCX every 15 minutes via SFTP, and load it into our internal Postgres table (ringcx.interaction_legs). We use that data to power a "Case Journey" view in our internal app, where reps can see all call activity for a given customer case.

We'd like to add an "Open in RingSense" button next to each call so reps can jump directly to the conversation page, e.g. https://ringsense.ringcentral.com/calls/3f2a8e12-966b-40e3-8ce5-baa40396437b.

The problem: the UUID in that URL isn't in our SFTP feed. We have:

  • UII (e.g. 202604271934311801140000038844)
  • ANI / DNIS
  • segment_start_time, segment_index
  • Agent name, disposition, queue, talk/wait/hold/wrap times
  • Recording URL (vacd.biz link)

But not the Segment ID (p-v-a531ab95...) or Dialog ID (s-v-a531ab95...) shown in the RingSense UI under "Source identifier," and definitely not the URL UUID itself.

A couple of questions:

  1. Can the Segment ID, Dialog ID, or the RingSense call UUID be added as columns in the Interaction Details report? I don't see them in the column-picker today, but I might be missing a setting.
  2. If not, is there an API endpoint that takes a UII (or ANI + start time) and returns the RingSense call UUID? I've looked at the analyze-interaction endpoint under /ai/insights/v1/... but that's for submitting new audio, not looking up existing calls.
  3. Or is there a search-style RingSense URL (like ?search=<UII>) that resolves a UII to the call page without needing the internal UUID at all?

Any of these would unblock us. Right now we're considering linking to a search results page as a fallback, but a direct deep-link would be much better UX.

Thanks!

Best answer by igor.patashvili

At the moment, RingSense data isn’t available in RCX Analytics Historical Reporting, and there’s no API access yet. This capability is on our product roadmap and is currently under architectural review.

1 reply

At the moment, RingSense data isn’t available in RCX Analytics Historical Reporting, and there’s no API access yet. This capability is on our product roadmap and is currently under architectural review.