Skip to main content
Use this page to get your production calls from Genesys Cloud into Bluejay Logs, so metrics, alerts, issues, and dashboards cover them.
Bluejay has no built-in Genesys Cloud connector. You run a small job that reads finished calls from Genesys Cloud and sends each one to Bluejay with POST /v1/evaluate.

How it works

For every finished call, your job does three things:
  1. Find. Ask Genesys Cloud which calls finished in a time window.
  2. Fetch. Ask Genesys Cloud for each call’s recording link.
  3. Send. Post the link to Bluejay. Bluejay downloads the audio, transcribes it, and runs your metrics.
The call then appears in Logs with its transcript and metric results. The script at the end of this page does all three.

Before you start

  • A Genesys Cloud admin who can create an OAuth client and edit Architect flows.
  • A Bluejay agent to file the calls under. Use one agent for each line or queue you want to track separately. To tell individual reps apart, see Track individual reps.
  • Somewhere to run a scheduled job, such as cron or a serverless function.

Steps

1

Make sure Genesys Cloud records the calls

Bluejay scores the audio, so each call needs a real recording. Turn on recording for the external trunk the calls arrive on.If an Architect flow handles the call, such as an IVR or a virtual agent, open the flow. Go to Settings > Recording and Speech Recognition and clear Suppress recording for the entire flow. Then publish the flow.The Recording and Speech Recognition settings of an Architect inbound call flow, with Suppress recording for the entire flow clearedIf that box is ticked, Genesys Cloud still lists a recording for the call. In our test it was about half a second long and had no download link. A new call after clearing the box and publishing returned a recording of the full call.If your trunk can record each side on its own channel, turn that on. The external trunk has the properties trunk_recording_enabled and trunk_recording_dualChannel.
2

Create an OAuth client in Genesys Cloud

The client gives your job read access to conversations and recordings.Search for OAuth and open IT and Integrations > OAuth. Click Add Client.The Genesys Cloud OAuth page with the Add Client buttonEnter an app name and a description, and choose the Client Credentials grant type. Click Next.The Add New Client form with the Client Credentials grant type selectedOn the Roles step, assign a role that can view conversation details and recordings, and choose the divisions your calls are in. The job uses two permissions, analytics:conversationDetail:view and recording:recording:view. A dedicated read-only role with only these is best. If a request returns 403, the error names the permission the role lacks.The Roles step of the Add New Client wizard, with a table of roles and an Assigned toggle on each rowFinish the steps 2. Allowed IP addresses and 3. Additional details, then save. Copy the Client ID and Client Secret into your secrets manager.
3

Create a Bluejay API key and find your agent ID

In Bluejay, open Settings > API Keys and click Create API Key. Copy the key into your secrets manager.The API Keys page with the Create API Key buttonOpen the agent the calls belong to and note its ID. If you set an external_agent_id on the agent, you can send that instead of agent_id.
4

Find the calls that finished

Get a token with your OAuth client, then query the voice conversations in your time window. Each conversation has a conversationId, the same ID the Interactions page shows.
The Genesys Cloud Interactions page with a Conversation ID columnEach conversation in the response has conversationId, conversationStart, and conversationEnd. Its participants have sessions that include the caller’s ani. Send only calls that have a conversationEnd.Use short windows, such as one day or less. In our test, an interval longer than about a month returned nothing.
5

Get each call's recording link

The mediaUri is a signed link. It carries its own access in the Expires, Signature, and Key-Pair-Id query parameters, so Bluejay needs no extra headers. It expires, so send it to Bluejay right away and do not store it.An empty mediaUris can mean that recording is suppressed. Check step 1.
6

Send the call to Bluejay

A successful response includes a call_id. The API allows 100 requests per minute for each organization, or 500 for enterprise accounts.Each request that changes a conversation is evaluated and billed. Bluejay ignores a repeat only when the transcript, transcript link, and recording link are all the same, and a signed link from Genesys Cloud can differ from one request to the next. Use windows that do not overlap, so each call is sent once. See the Logs page for how repeats work.
7

Check the call in Bluejay

Open Logs. The call appears as a new row under your agent after Bluejay processes the audio. Open it to read the transcript and see each metric’s result.The Logs page with one row for each conversationA conversation opened from Logs, showing its Evals tab with metric results

The script

This Python script does steps 4 to 6 for one time window. It uses only the standard library. It reads one page of up to 100 calls, so use windows that hold fewer calls than that.
This script is an example, not a supported tool. It has not been run end to end against a Genesys Cloud OAuth client. Run it on a few test calls first.
Run it on a schedule, such as every 15 minutes over the 15 minutes that just ended, with no overlap between runs.

Good to know

  • Region. Use your own Genesys Cloud region in the hostnames, such as mypurecloud.com or usw2.pure.cloud.
  • Recordings take a moment. Right after a call ends, the recordings request can return 202. The script waits and asks again.
  • More than 100 calls in a window. Raise pageNumber until Genesys Cloud returns no more conversations, or use shorter windows.
  • Skipped calls. The script waits about a minute for a recording link. If none arrives, it skips the call and does not try it again in a later window. Run the script again for that window, or send the call yourself.
Last modified on November 18, 2026