Reference · built on requestConnectorVoice & contact center

NICE CXone

Agent sessions, contact events, skills, reporting, and data extraction from NICE CXone through the DEVone developer APIs.

Request accessPricing ↗

About

NICE CXone is the cloud contact center suite sold by NICE. Its DEVone developer portal publishes REST API families that include Admin, Agent, Real-Time Data, Reporting, Data Extraction, Recording, Interaction Analytics, WFM, and Digital Engagement APIs. Every HTTPS request carries an access token issued through OAuth2, an Access Key, or OpenID Connect. Agent and contact events arrive by long polling an agent session rather than by webhook.

Through Fibric, an operator reads skill and agent activity, contact events, and historical reports, then proposes a skill assignment change, an agent message, or a remote logoff. A supervisor approves it and keeps a record of what changed and why.

This is a reference listing. It documents what Fibric would read from NICE CXone and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Agent, contact, chat, work item, and supervisor events by long polling GET /agent-sessions/{sessionId}/get-next-event with a timeout of 0 to 60 seconds
  • Skills, agents, groups, contacts, unavailable codes, and routing attributes as system objects in the Admin API
  • Agent and skill activity for dashboards and leaderboards through the Real-Time Data API
  • Historical contact and agent data over a defined time frame through the Historical Reporting (DW) and (DL) APIs
  • Interaction metadata and QM workflow data as extraction jobs through the Data Extraction API /jobs/sync endpoint
  • Recordings, media playback, and interaction analytics through their own API families

Proposed actions

  • Target capability: propose a skill assignment change for an agent through the Admin API
  • Target capability: propose a message to an agent through the AgentMessaging resource of the Admin API
  • Target capability: propose remotely logging off an agent, an admin-level function of the Admin API
  • Target capability: propose a custom event to an agent through PUT /agents/{agentId}/custom-event

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Move skills as the day drifts

    Compare skill and agent activity from the Real-Time Data API with the coverage plan. When a skill runs short, propose skill assignment changes for the shift lead to approve.

    With Intraday Balance

  • Summarize a call from its recording

    Pull the recording and interaction analytics for a contact, draft a summary and a coaching note, and hand both to the team lead to accept or edit.

    With Call Summary, Coaching Notes

  • Find what drives contact volume

    Extract interaction metadata in one-day windows through the Data Extraction API and group contacts by reason, so the weekly review shows which drivers grew.

    With Contact Drivers

  • Warn an agent before a breach

    Watch contact events on the agent session. When a handle time crosses your threshold, propose an agent message; the supervisor sends it or dismisses it.

    With Breach Watch

Requirements

  • A CXone user account for the integration with a role that grants only the permissions the app needs
  • The Access Key permission set to Edit on the account that generates the key
  • Discovery of your regional base URL, https://api-{area}.{domain}.com, from the well-known cxone-configuration endpoint for your tenantId
  • For FedRAMP tenants, the separate cxone-gov.niceincontact.com token host
Authentication
An Access Key ID and Access Key Secret generated by a CXone administrator for an integration user account, exchanged for an access token at https://cxone.niceincontact.com/auth/token.

Limits

  • Events are pulled by long polling an agent session; with no webhook push; a session belongs to the agent whose credentials fetched the token
  • Data Extraction allows one active job per tenant, at least 30 seconds between requests, and download URLs that expire after 30 seconds
  • New interaction data can take up to 30 minutes to appear in extraction results; Data Lake contact data needs 15 to 30 minutes
  • Access tokens carry a TTL; NICE advises renewing with the refresh token before 5 minutes of expiry

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request NICE CXone ↗

Questions and answers

Does NICE CXone push events to a webhook?
Not through the Agent API. Your application starts an agent session and calls get-next-event with a timeout between 0 and 60 seconds. The server answers with HTTP 200 when events exist or 304 when the timeout passes with none. NICE calls this the comet pattern.
How does a back-end integration authenticate?
An administrator generates an Access Key ID and Access Key Secret from a CXone user account set up for the integration. The app exchanges them for an access token at cxone.niceincontact.com/auth/token and discovers its regional API base URL from the cxone-configuration endpoint.
How current is historical data?
The Reporting APIs return data over a defined time frame, not the current moment. Contact data takes about 15 to 30 minutes to reach the Data Lake, and new interaction data can take up to 30 minutes to appear in Data Extraction results.
Ask about NICE CXone

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with NICE CXone through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy