Source type

Webex Source Configuration

Webex sources receive room, message, meeting, membership, and resource events with Webex secret signature verification.

WEBEXPOST, PUT, PATCH, DELETEWebhook SecretCommunication
Webex sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.WebexProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLWEBEXProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Webex configuration

Create a Webex source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Secret values for provider signature. FastHook uses these settings to validate each Webex delivery before it enters the routing workflow.

Source Type

WEBEX

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Secret

Webex source config
{
  "type": "WEBEX",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "WEBEX",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Webex request contract

FastHook computes HMAC-SHA1 hex over the raw body and compares it with x-spark-signature.

POSTPUTPATCHDELETE

Webex headers

Preserve x-spark-signature when sending Webex test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

x-spark-signature

HMAC-SHA1 hex signature over the raw body.

Webex setup

  1. Create a Webex webhook with the FastHook Source URL.
  2. Use the Webex webhook secret in FastHook.
  3. Use resource and event fields to route Webex traffic.

Continue with Webex