Sunshine Conversations is included with the Zendesk Suite plan. If you’re on Support Professional, use the Ticketing API path for email handoff and contact Zendesk to upgrade for real-time channels.
Before you start
Zendesk Suite plan with Sunshine provisioned
Zendesk Suite plan with Sunshine provisioned
Open Admin Center → Apps and integrations → APIs → Conversations API. If the section is missing, Sunshine isn’t provisioned on your account — contact Zendesk.
Admin access in Zendesk
Admin access in Zendesk
You’ll create an App key in the Conversations API section and note your . Agent roles don’t have access.
Owner or admin in OpenCX
Owner or admin in OpenCX
Required to save integration settings in Settings → Integrations.
Setup
Create a Sunshine App key
In Zendesk, open Admin Center → Apps and integrations → APIs → Conversations API.
- Click Create API key.
- Label it
OpenCX. - Copy the Key ID and Secret — Zendesk only shows the Secret once.
- Note the App ID displayed at the top of the page.
Open Zendesk Messaging in OpenCX
In OpenCX, go to Settings → Integrations, find Zendesk, and click Zendesk Messaging.
Enter your Sunshine credentials
| Field | Value |
|---|---|
| Subdomain | The acme part of acme.zendesk.com. Same subdomain used for Ticketing. |
| App ID | The Sunshine from the Conversations API page. |
| Key ID | The ID from the App key you just created — starts with app_. |
| Secret | The secret you copied. |
Provide a Zendesk API token for user merge
Sunshine uses a separate identity model from Zendesk’s support API. To prevent the same person from showing up as two separate , OpenCX merges Sunshine messaging contacts with matching Zendesk support users.In the Zendesk API credentials panel on the same page, reuse the credentials from the Ticketing API setup. The merge endpoint uses the same token. If you skipped Ticketing, generate a token for this purpose alone — user search is free on every Zendesk plan, and no webhook is needed.
What OpenCX writes on every Sunshine conversation —
metadata.opencx_org_id, metadata.opencx_contact_id, and metadata.opencx_session_id. Your reps don’t see these fields directly, but they’re reachable via the Conversations API for debugging and analytics. The session ID is the trace key back to the exact OpenCX conversation.Copy your messaging webhook URL
After saving, OpenCX displays a Messaging Webhook URL. Keep it handy — you’ll paste it into Zendesk next.
Register the webhook in Sunshine
In Zendesk’s Conversations API admin, open the Integrations / Webhooks panel for your app and add a new webhook.
Save the webhook.
| Field | Value |
|---|---|
| Target URL | Paste the OpenCX messaging webhook URL. |
| Triggers | conversation:message (required). conversation:read optional, for read receipts. |
| Secret | Leave blank — OpenCX validates by signed URL. |
Verify end to end
Send a test message on a connected messaging channel (web widget, WhatsApp sandbox, or SMS). Escalate the conversation.
- The conversation appears in the Zendesk Agent Workspace as a live chat.
- Reply from the Agent Workspace.
- The reply lands back on the original channel within a couple of seconds.
Sunshine channels handle off as live chats, not tickets
For channels routed through Sunshine — WhatsApp, Messenger, Instagram, web chat, SMS, and phone — handoff does not create a Zendesk ticket. The conversation appears in the Agent Workspace as a live chat. Ticket-based behavior (AI Fields auto-fill, tag application, agent-reply sync) described on the Ticketing API page applies to email only.Rotating Sunshine credentials
Create a new App key in Zendesk, paste it into OpenCX, then delete the old key. The is unaffected by App key rotation.Disconnecting
Click Disconnect on the Zendesk Messaging card in Settings → Integrations. Then delete the webhook in the Conversations API admin. Active conversations finish out on their current channel; no data is deleted from Zendesk.Related Documentation
Channels
Per-channel implementation details for Widget, WhatsApp, SMS, Phone, and Email.
Ticketing API
The companion path for email handoff.
Assist Mode
AI-drafted internal notes on tickets your reps already own.
Troubleshooting
Agent Workspace not receiving messages, duplicate users.