Webex Events (formerly Socio)

Webex Events (formerly Socio) Integration Guide

Overview

This guide explains how to connect Bridged with Webex Events (formerly Socio) to read event content including attendee data, agenda/session information, speaker profiles, exhibitor details, and sponsor information. The integration supports reading this data for activation, qualification, and nurture playbooks where event context is needed.

Webex Events is an event technology platform acquired by Cisco that helps organizations manage in-person, virtual, and hybrid events. The platform provides a GraphQL API for programmatic access to event data .

Primary Use Case: Read Event Content

For Bridged's event experience integrations, the primary use case is reading event-related data, including:

Prerequisites

Before starting, ensure you have:

⚠️ Important: API access is not automatically available. If you're not a Webex Suite Enterprise Agreement customer, you must contact Webex Events support to request API access .

Step 1: Verify API Access

API access is automatically included for Webex Suite Enterprise Agreement (Suite EA) customers. For all other customers, contact your Webex Events representative or support team to request API access .

When API access is enabled, a new API tab appears in the Organization settings page .

Step 2: Create an API Key

⚠️ Warning: This is the only time the full API key can be accessed. After closing the modal, the full key cannot be retrieved again .

Step 3: Configure Bridged to Connect to Webex Events

Step 4: Understanding the GraphQL API

Webex Events uses a GraphQL API, not REST. This means you query exactly the data you need using GraphQL query syntax .

Basic Query Example

graphql

query EventsConnection($first: Int) {
    eventsConnection(first: $first) {
        edges {
            cursor
            node {
                id
                name
                groups {
                    id
                    name
                }
            }
        }
    }
}

Query with Variables

graphql

query GetEventSessions($eventId: ID!) {
    event(id: $eventId) {
        id
        name
        sessions {
            id
            title
            startTime
            endTime
        }
    }
}

Variables:

json

{
    "eventId": "YOUR_EVENT_ID"
}

Step 5: Available Data Types

Based on Webex Events API documentation, the following data can be read :

Event App Components

The API can also read Event App features including :

Step 6: Configure Sync Settings

Bulk sync limit: Each bulk operation is limited to 50 records per request.

Pagination

GraphQL queries use cursor-based pagination with first and after parameters:

graphql

query {
    eventsConnection(first: 50, after: "cursor_value") {
        edges {
            cursor
            node { id name }
        }
        pageInfo {
            hasNextPage
            endCursor
        }
    }
}

Step 7: Alternative - Invite Developers to API Sandbox

If you need to test the integration without affecting real event data, Webex Events provides an API sandbox environment :

Note: All new members of the API Sandbox team must create a new platform account for the sandbox, even if they already have a production account .

Common Use Cases

Example Conversation Powered by Webex Events Data

When an attendee asks "What sessions are tomorrow?", Bridged:

Limitations & Considerations

Rate Limiting & Performance

Security & Permissions

Idempotency for Mutations

For mutation operations (create/update/delete), the API supports idempotency keys to safely retry requests without duplicate operations :

text

Idempotency-Key: <unique_key>

Troubleshooting

Support

For integration support, contact your Bridged account manager or email support@bridged.media.

For Webex Events-specific questions: