Reference · built on requestConnectorVoice & contact center

Five9

Campaigns, skills, users, contacts, and reports from Five9 through its Configuration Web Services and Agent and Supervisor REST APIs.

Request accessPricing ↗

About

Five9 is a cloud contact center platform sold by Five9. Its Configuration Web Services API is a SOAP service described by a WSDL at api.five9.com/wsadmin, versioned v12 and v13, and authenticated with the username and password of an administrator. A separate Agent and Supervisor REST API starts a session from a metadata endpoint that names the data center for your domain. Five9 publishes the reference guides to members of its Developer Program and keeps code samples in the Five9DeveloperProgram organization on GitHub.

Through Fibric, an operator reads campaigns, skills, users, and report output, then proposes a calling list record, a contact update, or an agent group change. Your administrator approves it and the record shows what changed.

This is a reference listing. It documents what Fibric would read from Five9 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

  • Campaigns, skills, users, and agent groups through getCampaigns, getSkills, getUsersInfo, getUsersGeneralInfo, and getAgentGroups
  • Contact records and dialer counters through getContactRecords and getCallCountersState
  • Report output through runReport, getReportResult, and getReportResultCsv
  • Agent presence and call interactions through the Agent REST API at /agents/{agentId}/presence and /agents/{agentId}/interactions/calls
  • Domain queues and supervisor statistics through the Supervisor REST API, including GET /orgs/{orgId}/skills

Proposed actions

  • Target capability: propose a record added to a calling list through addRecordToList or addRecordToListSimple
  • Target capability: propose contact field updates through updateContacts
  • Target capability: propose a skill or agent group change through createSkill, modifyAgentGroup, and modifyUser

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

What you can build

  • Schedule a callback for a detractor

    When a survey score falls below your line, propose a record on a callback calling list through addRecordToListSimple. A supervisor confirms the list and the time window.

    With Detractor Callback

  • Watch queue wait before it breaches

    Poll supervisor statistics for each domain skill. When wait time crosses your threshold, name the agents to add through modifyAgentGroup and ask for approval.

    With Breach Watch

  • Match presence to the schedule

    Read agent presence through the Agent REST API and compare it with the published roster. Flag gaps and propose who should cover them.

    With Shift Coverage

  • Draft a coaching note from report output

    Run a call log report through runReport, pull the CSV, and draft a coaching note for the team lead to accept or edit.

    With Coaching Notes

Requirements

  • A Five9 domain and an administrator account with Admin Web Service access and permissions for the objects you query or modify
  • Membership in the Five9 Developer Program for the API reference guides
  • A SOAP client that can load the wsadmin WSDL for version v12 or v13
  • The data center for your domain (US, CA, LDN, or FRK), read from the metadata endpoint before any REST call
Authentication
Basic authentication over HTTPS with a Five9 user granted Admin Web Service access; the Agent and Supervisor REST APIs start a session from the metadata endpoint at app.five9.com.

Limits

  • The WSDL endpoints answer HTTP 403 without credentials, so the service description itself needs an authenticated client
  • Five9 enforces rate limits that vary by tenant and are not published; bulk operations need pacing when throttling appears
  • Agent and Supervisor REST calls run inside a session started for one agent or supervisor, not an account-wide token
  • Configuration Web Services is SOAP over HTTPS; the public material documents no webhook feed

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 Five9 ↗

Questions and answers

Where are the Five9 API reference guides?
Five9 publishes them to members of its Developer Program. The public development page links the program and the Five9DeveloperProgram organization on GitHub, which holds a Python wrapper for the Configuration Webservices API and a starter kit for the Agent and Supervisor REST API.
How does the Agent REST API find its host?
Your client first calls the metadata endpoint at app.five9.com/appsvcs/rs/svc/auth/metadata. The response names the data centers and the apiUrlBase for your domain. The client then starts a session with /agents/{agentId}/session_start and calls methods under that base.
Does Five9 publish rate limits?
No figures appear in the public material. The Five9DeveloperProgram module for the Admin Web Service states that rate limits are enforced by Five9, vary by tenant, and that bulk operations should add delays when throttling appears.
Ask about Five9

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 Five9 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