The short version: Five9 sells a modern cloud contact center. What you integrate with is a platform where SOAP still runs the administrative functions that matter — users, campaigns, lists, skills, reporting — while newer REST endpoints handle agent-facing operations, audio streaming, and transcript delivery. There are no official SDKs in any language, no public OpenAPI specs, and the AI capabilities everyone's marketing don't have programmatic APIs. The platform rewards pre-built CRM adapter deployments and punishes custom builds. If your plan assumes "API-first," you'll find the edges fast.

Why Does Five9 Still Use SOAP in 2026?

Because the administrative core was built that way, and they've never migrated it.

Five9's API surface is two generations running side-by-side with no overlap and no convergence timeline.

Configuration and admin: SOAP. Users, campaigns, calling lists, skills, contact records, dispositions, IVR scripts, reporting jobs — all of it goes through the Configuration Web Services API at api.five9.com/wsadmin/v[version]/AdminWebService?wsdl with HTTP Basic Auth. The Statistics and Supervisor Web Service follows the same SOAP pattern. The reference guide was last formally updated September 2021, though WSDL versions have incremented through v12.

Real-time agent operations: REST and WebSockets. The Agent and Supervisor REST API handles session management, call control, state changes, and supervisor monitoring. WebSocket support provides event streaming for active sessions. VoiceStream (launched September 2020) delivers real-time audio streaming via SIP, gRPC, and SIPREC. TranscriptStream (announced June 2024) is the newest REST-based addition — real-time speech-to-text feeds now central to Five9's Fusion integrations with ServiceNow and Salesforce.

There is no publicly announced REST replacement for the admin APIs and no deprecation timeline for SOAP. An Events Subscription API visible at developer.alpha.us.five9.net signals Five9 is experimenting with API-first event management, but it remains in alpha. Five9's 2024–2025 investment has focused on AI capabilities and streaming APIs, not modernizing the administrative surface.

What this means operationally: your automation backlog — provisioning, routing configuration changes, bulk reporting pipelines — carries more engineering overhead than it should. Not because your team is weak. Because you're integrating into an administrative core that predates the current decade's expectations for developer experience.

What Are Five9's Real-Time Data Options?

Better than people think, but segmented in ways that matter.

A lot of Five9 takes get this wrong in both directions. Some folks assume it's all polling. Others assume it's all event-driven. The truth is: Five9 distributes real-time data across five distinct mechanisms with different protocols, scopes, and trade-offs. There is no unified event bus — no Kafka, no EventBridge, no general-purpose pub/sub.

Event Subscription Service (ESS): actual push, actual webhooks. ESS remains the primary webhook mechanism for interaction lifecycle events — disposition set, agent ended, call created. Configured in the Admin Console, it delivers events via HTTPS POST or to file-based destinations (S3, FTP/SFTP, Google Cloud Storage). It supports field filtering on attached variables, custom HTTP headers for authentication, and retry logic for delivery failures. The scope limitation is real: ESS does not cover real-time agent state changes, queue statistics, or campaign-level events. It's not a general event stream.

WebSockets for agent and supervisor sessions. Five9's REST APIs can open a WebSocket for an active authenticated session to receive real-time events. Supervisor WebSockets expose nine data sources: ACD_STATUS, AGENT_STATE, AGENT_STATISTIC, CAMPAIGN_STATE, inbound/outbound campaign statistics, outbound campaign manager, stations, and user sessions. Each connection consumes a licensed user seat. This architecture makes WebSockets unsuitable as a backend event bus — they're designed for dashboards and supervisor tools, not server-to-server integration.

VoiceStream: the "data out" pipe for serious AI. VoiceStream is the strategic asset for real-time audio streaming to external AI systems. Two deployment models exist. The partner model uses the VoiceStream Directives API for accredited partners — Cresta, CallMiner, Cogito/Verint, Uniphore, ValidSoft, XSELL, Birch.ai, MiaRec, Calabrio — to receive SIP-based audio streams. The self-service model lets customers configure streaming destinations directly: primary SIP or gRPC endpoint, secondary failover, CTI call event webhook, and stream status webhook. Key constraints: maximum 10 VoiceStream subscriptions per domain, and stereo separation delivers agent and customer channels as separate SIP sessions. Google Cloud published open-source middleware for connecting VoiceStream to Dialogflow Agent Assist via gRPC.

TranscriptStream: the newest and arguably most important pipe. Rather than streaming raw audio, TranscriptStream delivers real-time speech-to-text transcription feeds. It powers Five9 Fusion for ServiceNow (GA September 2025), where transcripts flow into ServiceNow Workspace for Now Assist to generate AI summaries and recommended actions. It similarly feeds Salesforce Einstein AI in the Fusion for Salesforce integration. TranscriptStream represents Five9's strategic bet that partners and customers increasingly want processed text, not raw audio, for AI pipelines. If you're designing a new AI integration against Five9 today, TranscriptStream is likely your starting point.

Workflow Automation (WFA) webhooks. WFA became a standard platform capability in March 2023. It provides visual, low-code orchestration with inbound/outbound webhook support, trigger scanning on VCC events (disposition, agent state, queue thresholds), and a solutions catalog of automation templates. It's business-user oriented rather than developer-grade — a managed orchestration platform, not a raw event streaming API. Useful for bridging gaps where a direct API isn't available.

Operator takeaway: you can build real-time systems on Five9. Just don't confuse ESS (interaction lifecycle webhooks), WebSockets (session-tied supervisor data), VoiceStream (raw audio streaming), TranscriptStream (real-time transcription), and WFA (low-code orchestration). They solve different problems and don't share a single event model.

How Long Does Five9 Keep Your Data?

Not long. And the answer varies by data type in ways that catch people.

Five9's official Data Retention Policy confirms the defaults:

• Call logs: 60 days (except as required by state/federal law)

• Contact data: 120 days after end of contract

• Agent data: 60 days

• Call recordings: 30 days — with a critical nuance: retention is "sooner of 30 days OR successful offload via SFTP/FTP, or per contract." Recordings may be purged before 30 days once successfully offloaded.

• Omnichannel (email, chat, social): 60 days, with variable online search retention up to 2 years for email and chat

• Campaign state and dialing lists: 120 days

• IVA Studio configuration: Indefinite. IVA logging: 30 days.

Five9 explicitly reserves the right to "periodically purge Customer data from Five9 owned servers" due to storage demands. SFTP is strongly recommended over FTP for recording offloads. Additional storage is available for a fee through Five9 sales.

This shapes everything. If you need year-over-year trending, long-horizon forecasting, post-mortems beyond 60 days, or regulatory retention (FINRA, MiFID II, HIPAA audit trails), you need continuous export pipelines from day one. If you wait until renewal season to ask why your history is gone, you're already too late.

Reporting reality: you're doing asynchronous report jobs via SOAP, paging and chunking results, and normalizing timezones. The operational cost isn't "the report." It's the pipeline you build to make reporting reliable across the 60-day window before your data vanishes.

Can You Programmatically Control Five9's AI?

Not really. The AI products are real. The APIs aren't.

Five9 has consolidated its AI portfolio under the Genius AI umbrella: AI Agents, Agent Assist, AI Summaries, AI Insights, AI Knowledge, GenAI Studio, and AI Trust & Governance. The "Agentic CX" direction announced at CX Summit 2025 is genuine investment. But for architects, the critical question is programmability — and the answer is: almost none.

GenAI Studio (announced March 2024, GA second half of 2024) is an LLM-agnostic prompt management hub supporting OpenAI GPT, Google Gemini, Meta Llama, and bring-your-own models. It provides a visual interface for creating, versioning, testing, and deploying prompts — initially scoped to AI Summaries customization. It is entirely GUI-based. No SDK. No CLI. No REST API for programmatic control. You can customize what the AI does through the UI. You cannot automate, version-control, or CI/CD those customizations through code.

IVA Studio offers no-code/low-code IVA development with a drag-and-drop builder, 40+ pre-built application templates, engine-agnostic NLU (supports Google Dialogflow, Amazon Lex, IBM Watson, Microsoft), and "power developer" tools including JavaScript functions and API calls within dialog flows. If you're bringing external AI models in, the realistic pattern is: Studio calls your service, your service returns something (intent, summary, classification), Studio routes accordingly. There is no external API to programmatically create, modify, or deploy IVAs.

Agent Assist and the Connectors question. The original version of this article stated that custom AI output cannot be injected into the native Five9 agent desktop UI. That's partially wrong. Five9's Connectors mechanism allows third-party web applications to be embedded via iframe directly within Agent Desktop Plus. Connectors are configured with a URL endpoint and trigger events (On Call Accepted, On Chat Arrival), and Five9 passes session parameters — session_id, domain_id, skill_name, campaign_name. Kore.ai embeds its Agent AI widget (coaching, playbook, sentiment, summaries) inside the Five9 desktop this way. Glance embeds cobrowsing through the same mechanism.

But these are sandboxed iframe embeds, not deeply integrated native UI elements. Five9's own Agent Assist has richer native integration than anything a third party can achieve through Connectors. A more accurate statement: third-party AI can appear within the Five9 desktop via Connectors, but as sandboxed web views with documented limitations — constrained data passing in some modes, no internal transfer support in certain scenarios, and concurrent chat constraints.

Latest Genius AI additions (CX Summit 2025, November): Agentic Quality Management (AI-powered evaluation of 100% of interactions with automated scoring and proactive SLA alerts), Genius Routing (dynamic API-driven matching using customer attributes, agent proficiency, and real-time AI insights), and Five9 AI Agents (autonomous voice and digital AI agents with adjustable trust levels, in beta since Q1 2025). These are promising capabilities — but none ship with public APIs for external orchestration.

The AI framework, summarized for architects:

• UI-configured AI: IVA flows, Agent Assist, AI Summaries, dashboards — configured and consumed inside Five9 tools. No programmatic control.

• Studio orchestration: Where "bring your own AI" lives. Studio calls your service, your service returns output, Studio routes. This works.

• Data-out for your AI stack: VoiceStream (raw audio) and TranscriptStream (real-time text) are how you get raw material to your own models. This is the most architecturally sound integration path.

• Connectors for agent-side display: iframe-embedded web views inside the desktop. Functional but sandboxed.

If your AI strategy is "live transcript → model → compliance alert → coaching," the VoiceStream/TranscriptStream + events path is how you get there. If your AI strategy requires programmatic control of Five9's native AI features, you're waiting for APIs that don't exist yet.

Does Five9 Have WFM APIs?

No. Zero public API endpoints for workforce management.

Five9 offers native Workforce Engagement Management through its February 2020 acquisition of Virtual Observer and white label relationship with Community WFM, with Essentials WFM (up to roughly 100 seats) and Enterprise WFM (advanced forecasting, shift bidding, PTO, adherence dashboards). The product includes quality management, interaction analytics, performance dashboards, gamification, and recording with 256-bit AES encryption.

But the WFM layer has no APIs. No endpoints for programmatic schedule management, PTO workflows, real-time adherence data, quality scores, evaluation results, or gamification data. The SOAP-based reporting API covers contact center operational data only — not workforce data.

If WFM automation (schedules, PTO workflows, adherence actions) is a core requirement, treat it as a separate evaluation track — not an assumption bundled into "we bought Five9."

The partner landscape is where this gets interesting. Verint has the deepest integration — hosted on Five9 infrastructure with a shared data layer and unified UI — and has been the primary enterprise WFM partner since 2016. Calabrio integrates via VoiceStream for real-time audio streaming. Playvox uses scheduled API polling (agent states every 10 minutes, call logs every 15 minutes). In September 2025, Thoma Bravo announced a $2 billion acquisition of Verint to merge it with Calabrio — a development that could significantly reshape Five9's WFM partner landscape and potentially force Five9 to either deepen its native WFM capabilities or build WFM APIs to reduce dependency on a now-consolidated partner. Architects should monitor this closely.

What's the Developer Experience Actually Like?

The weakest dimension of the platform. And it's not close.

Five9's developer ecosystem is strikingly small for a platform serving 3,000+ customers. There are zero Stack Overflow tags or questions for Five9 APIs, no meaningful Reddit developer discussions, and the official GitHub organization's most popular repository has 12 stars. The Developer Program self-reports "hundreds of active members" — not thousands.

No official SDKs exist. Not in Python, not in Node.js, not in Java, not in Go. The 14 public repositories under github.com/Five9DeveloperProgram all carry a prominent disclaimer: sample code that is "not an official Five9 resource" with "no liability" and "no support" — explicitly directing developers to paid Professional Services for production implementations.

Community-built wrappers are fragmented and largely unmaintained. The most substantial Python library (python-five9 by LasLabs) remains in perpetual beta at v0.0.3b192, with its author describing Five9's data structures in source code comments in terms that won't make it into marketing materials. A Go SDK exists (five9-go) but has minimal adoption. No Node.js wrapper exists at all.

The CRM SDK is the exception. Well-documented JSDoc at cdn.prod.us.five9.net/stable/crm-sdk-lib/doc/, publicly accessible, with comprehensive API coverage: InteractionApi, CrmApi, HookApi, ApplicationApi, PresenceApi, and the CustomComponentsApi for registering custom UI components within the CRM adapter experience. If you're building within Five9's CRM adapter model, the developer experience is genuinely good.

Pain points documented across forums, blog posts, and community discussions:

• SOAP complexity is the persistent top frustration, unchanged from 2015 to 2026. Developers accustomed to REST + JSON find the WSDL discovery, XML envelope construction, and SOAP fault handling genuinely painful.

• Multi-step authentication requires initial metadata discovery before API calls, confusing developers accustomed to standard OAuth or API key patterns.

• Documentation behind login walls. Most docs require Developer Program membership. They're delivered as PDFs rather than interactive API references. No OpenAPI/Swagger specs. No public Postman collections.

• No public API changelog. No documented rate limits. No public status page for API availability (Five9's status page at status.five9.com is gated behind subscriber login — unusual for a SaaS vendor).

• Integration finger-pointing. When custom integrations break, the documented troubleshooting path often routes between Five9 and partner support organizations with different SLAs.

The Five9 Marketplace ecosystem is real and growing — it's where many "advanced capabilities" are delivered via accredited partner integrations rather than native APIs. This is one of Five9's pragmatic operator strengths: the platform is built to be used at scale through sanctioned partner paths, not admired in architecture diagrams.

Is Five9's 99.999% SLA Real?

The number is published. The fine print matters.

Five9's SLA at five9.com/legal/sla-service-level confirms a 99.999% Targeted Uptime commitment across all service categories — VCC Voice, Email, Chat, WFO, and AI. Service credits begin at 5% for availability below 99.990% and reach 100% below 97.000%. A chronic failure clause allows termination after three consecutive months of missed targets.

The exclusions are broad enough to materially narrow what counts as downtime: customer network and equipment issues, scheduled maintenance, and critically, third-party voice connectivity, natural language, and speech synthesis provider interruptions. For a contact center platform where telephony is the core service, excluding carrier-level outages is a meaningful carveout. The per-user availability calculation further dilutes partial outages — an incident affecting 10% of users for one hour registers proportionally, not as one hour of total downtime.

The "444+ tracked outages since December 2021" figure that circulates online requires context. It originates from StatusGator monitoring of CallTower's Five9 status page — a reseller, not Five9's own infrastructure. The count includes all status changes across 36 components using four statuses (up, warn, down, and maintenance), meaning routine maintenance windows and warning states are counted alongside actual service degradation. It's a noisy signal, not a clean incident count.

That said, Five9's own status page being gated behind subscriber login makes independent verification of uptime claims difficult — an unusual practice among enterprise SaaS vendors and one that legitimately frustrates prospects doing due diligence.

Current compliance certifications: SOC 2 Type II, ISO 27001:2022, ISO 27017:2015 (cloud-specific, appears recently added), PCI DSS Level 1, HIPAA (Business Associate Agreement available), Cyber Essentials, Texas RAMP Level 2, and StateRAMP membership. Data centers operate in Ashburn VA, Chicago IL, Frankfurt, and Amsterdam, with EU data residency available since May 2022. Encryption covers data in transit (HTTPS, sFTP, sRTP, VPN) and at rest (optional, required for PCI compliance).

For regulated operations — healthcare, financial services — Five9's compliance posture is enterprise-grade. You can spend your energy on workflow controls instead of rebuilding baseline compliance infrastructure. That's a real advantage. Just read the SLA exclusions before you assume what "five nines" means for your specific uptime requirements.

Where Does This Leave You?

Five9 makes sense when:

• Outbound is core and you need mature predictive, preview, and progressive dialing.

• You need proven CRM adapters with a well-documented CRM SDK.

• You can live with SOAP for admin automation (or you're not automating admin at all).

• You're prepared to build export pipelines early — day one, not quarter three.

• Your AI plan is "data out + orchestration" — VoiceStream/TranscriptStream feeding your own models, Studio calling your own services — not "full programmatic control of Five9's native AI."

• You're routing through the Marketplace partner ecosystem rather than building custom integrations from scratch.

Five9 is a bad fit when:

• You require consistent REST coverage for administrative control and your team won't write SOAP.

• You need a unified event bus model — not session-tied WebSockets in some places, ESS webhooks in others, and WFA in the gaps.

• You need to programmatically manage AI features — deploy prompts, version IVA flows, automate QM evaluations via API.

• WFM automation is non-negotiable and you need API-driven schedule management.

• Your developer team expects modern DX — SDKs, OpenAPI specs, interactive docs, public changelogs, Postman collections.

Three things to watch. First, TranscriptStream is the most architecturally significant addition since VoiceStream — it signals Five9's direction toward providing processed intelligence streams rather than raw data, and will likely become the primary integration point for AI pipelines. Second, the Verint-Calabrio merger under Thoma Bravo could force Five9 to either build real WFM APIs or deepen its native WFM product to reduce dependency on a now-consolidated partner. Third, the alpha Events Subscription API hints at eventual API-first event management, but the pace of SOAP-to-REST migration has been glacial — plan for years, not quarters, of dual-protocol reality.

Monday Morning Move

Before you sign, or before you renew, do four tests in sandbox:

1. Prove your admin automation path. Stand up the SOAP Configuration Web Service. Create a user, assign a skill, add contacts to a list. Time how long it takes your team to get a working round trip. That time multiplied by every operational change you'll automate is your real integration cost.

2. Map your real-time architecture. Identify which of the five mechanisms (ESS, WebSockets, VoiceStream, TranscriptStream, WFA) solves each of your real-time requirements. If you need data that doesn't fit any of them, that's a gap you need to quantify before commitment.

3. Run the data retention math. Pull Five9's published retention policy. Map every data type your compliance, analytics, and operations teams need against those retention windows. Build the export skeleton on day one. Five9's retention defaults are a design input, not a surprise.

4. Test the Connectors boundary. If your AI strategy involves custom agent-side guidance, build a proof of concept through Five9's Connectors iframe mechanism. Identify exactly which session parameters you receive, what data you can pass back, and where the sandbox constraints limit your UX. Know the boundary before you promise the outcome.

Five9 is legitimately strong in outbound. CRM adapters are mature. VoiceStream and TranscriptStream are the real deal. Their compliance posture is enterprise-grade. But if you're trying to build unified CX infrastructure: technology, AI, and human agents working as a system, then you need to know where the platform helps and where you'll be the one paying the engineering tax.

InflectionCX operates unified customer experience operations, combining AI systems with human expertise across multi-state contact center operations. If you're evaluating Five9 or any CCaaS platform and want technical guidance grounded in operational reality, we're easy to find.