Running on Zoom?

Zoom webhooks or SSO failing? We fix it.

Zoom works well until a webhook signature starts failing because the verification token was swapped for the secret token three months ago, a SAML assertion rejects a renewed certificate, or the Meeting SDK refuses to join a session because the JWT signing method moved to OAuth. We trace the webhook signing, the SSO assertion, and the SDK token lifecycle until the integration behaves again.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

zoom-webhook.log

still failing

What it is

Zoom at a glance

Zoom is a video communications platform founded in 2011 by Eric Yuan, a former Cisco Webex engineer. The company became the default video meeting tool for many organisations during 2020 and has since grown into a broader platform covering meetings, webinars, phone, team chat, rooms, events and a developer marketplace for apps and integrations.

The platform offers meetings, webinars, Zoom Phone, Team Chat, Rooms, Events, a REST API with OAuth 2.0 (replacing the deprecated JWT app type), Server-to-Server OAuth, webhooks with HMAC-SHA256 signatures, the Meeting SDK for embedding meetings into other products, Video SDK for custom video experiences, and a Marketplace for publishing apps. It supports SAML SSO through most major identity providers, SCIM provisioning, data residency, encryption-at-rest and end-to-end encryption for meetings. Common issues we see are webhook signature mismatches after the recent move from Verification Token to Secret Token, SAML failures after certificate rotations, Meeting SDK integrations that still use the deprecated JWT credentials, and Server-to-Server OAuth tokens that expire inside hot paths because the integration did not implement refresh.

Type
Video communications and unified communications platform
First released
2013
License
Proprietary SaaS, per-user pricing with Basic, Pro, Business, Business Plus and Enterprise tiers
Maintained by
Zoom Video Communications, Inc.
Typically used for
Video meetings, webinars, phone, team chat, embedded video experiences via SDKs

The honest version

Zoom pros and cons

No technology is all upside. This is where Zoom earns its place and where it tends to cause trouble.

Where Zoom is strong

  • Reliable at scaleZoom handles very large meetings and webinars without the quality collapse that other platforms hit. For high-stakes company all-hands or large external events, it remains the safe choice.
  • A proper developer platformREST API, OAuth 2.0, Server-to-Server OAuth, webhooks, Meeting SDK, Video SDK and a Marketplace mean custom integrations and embedded video are real options rather than hacks.
  • Decent recording and transcriptionCloud recording, automatic transcription in many languages, speaker identification and shareable links cover the common needs without a third-party recorder.
  • Zoom Phone replaces a PBXThe phone product is a serious enterprise PBX replacement with call queues, auto attendants, international dial plans and native integrations that make it a credible alternative to legacy voice systems.
  • Enterprise administration is strongSAML SSO, SCIM, data loss prevention, end-to-end encryption, data residency and audit logs let security teams approve Zoom in regulated environments.
  • Marketplace apps extend workflowsSlack, Teams, Salesforce, HubSpot, calendar and CRM integrations in the Marketplace cover most of the glue work a mid-size org needs.

Where Zoom bites

  • The JWT to OAuth migration is painfulZoom deprecated the JWT app type and many existing integrations were built against it. Rewriting to OAuth or Server-to-Server OAuth is not a config change; it is a code change with new token lifecycles and new permission models.
  • Webhook signing changed and broke integrationsThe move from Verification Token to Secret Token with HMAC-SHA256 signing has caught many webhook consumers that were never updated. Deliveries succeed at Zoom and fail silently at your end.
  • Server-to-Server OAuth tokens are short-livedAccess tokens expire in an hour, and integrations that cache the token without refresh handling break mid-day without a clear error.
  • Meeting SDK requires careful JWT signingThe Meeting SDK needs JWTs signed with specific algorithms and specific claims, and the error messages are terse. Teams frequently misuse the SDK Key, API Key or OAuth credentials for SDK signatures.
  • Per-user pricing adds upPro, Business and Enterprise tiers add real cost per seat, and features like webinars, large meeting rooms and cloud recording minutes are additional line items.
  • Marketplace review is strict and slowPublishing an app for public install requires a security review and iteration cycles that can take weeks. Teams building for their own account can install intra-account more quickly but hit the same gates for public distribution.

Sound familiar?

Common Zoom problems we fix

The Zoom problems that bring people to us, and what you have once each one is fixed.

webhook signature verification failed

Webhook signatures stopped verifying

A consumer that was still using the old Verification Token to compare, rather than computing HMAC-SHA256 of the request body with the Secret Token and matching against x-zm-signature. Deliveries succeed at Zoom and are quietly discarded on your end.

Webhook signatures verify on current scheme

URL validation failed: plainToken not returned

Webhook endpoint fails URL validation

A newly configured webhook whose endpoint does not implement the challenge-response that Zoom requires on setup, returning the plainToken with its HMAC within three seconds. The webhook never finishes activating.

Endpoint handles validation handshake

Server-to-Server OAuth token expired

Server-to-Server OAuth tokens expire mid-request

An integration that fetched an access_token once at startup and never refreshed, hitting 401 after one hour. Automation fails around the top of the hour with a confusing error.

Token refresh handled automatically

SAML assertion signature invalid

SSO stops working after an IdP certificate rotation

An identity provider that rotated its SAML signing certificate without the new certificate being uploaded on the Zoom side, or a tenant alias that no longer matches the audience value. The entire org cannot log in through SSO.

SSO on current certificate

Meeting SDK: signature invalid

Meeting SDK rejects the signature on join

A JWT signed with the SDK Key and Secret but using the wrong algorithm, wrong claims structure (missing role or exp), or using Marketplace OAuth credentials where SDK credentials are required. Users cannot join embedded meetings.

SDK JWT signed correctly

deprecation: JWT app type

Legacy JWT integrations stop working

A JWT app type that hit the end-of-life date and now returns 401 on every call. The integration was probably built years ago and needs a rebuild rather than a config change.

Migrated to OAuth or Server-to-Server OAuth

429 QPS limit exceeded

API rate limits throttle bulk work

A reporting job or an export that lists users or meetings without respecting the per-endpoint QPS limit, which varies by endpoint and plan. The job completes with gaps.

API client paced per endpoint

SCIM duplicate email

SCIM provisioning stalls on duplicates

Users present in two IdP groups both syncing to Zoom, triggering duplicate email errors on the SCIM endpoint. New hires sit in a pending state until the IdP is cleaned up.

SCIM mapping deduplicated

What we do

Zoom help, webhook to SDK

Call us for one failing integration, or let us own the whole Zoom integration and developer surface.

Rescue
Webhooks silently rejected, SSO locked out, or a Meeting SDK that will not sign. We stabilise the connection first and explain the cause second.
JWT to OAuth migration
Legacy JWT integrations rewritten against OAuth 2.0 or Server-to-Server OAuth, with scopes audited, refresh handling implemented, and the new app registered correctly in the Marketplace.
Webhook consumers
URL validation handshake, Secret Token signature verification, idempotent handlers and reconciliation jobs that cover retry-budget exhaustion during outages.
Meeting SDK and Video SDK
Embedded meeting and custom video experiences, with JWT signing handled server-side, SDK key rotation planned and the browser-permission edge cases documented.
SSO and SCIM
SAML against Okta, Azure AD, Google Workspace or Ping, with certificate rotation schedule, SCIM provisioning and the tenant edge cases that Zoom's docs do not spell out.
Managed Tech
Deprecation watch for API and SDK changes, webhook signature monitoring, SSO certificate rotation reminders, and an engineer available when a Zoom release changes behaviour mid-quarter.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Zoom alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Zoom questions

Something else? Call+1 737 727 7327

Why are our Zoom webhook signatures suddenly failing?

Because the signing scheme changed from a simple Verification Token comparison to an HMAC-SHA256 signature computed with the Secret Token over the raw request body, delivered in the x-zm-signature header along with x-zm-request-timestamp. Consumers that were not updated continue to receive deliveries but reject them. We rebuild the verification against the current scheme and verify a sample delivery before pushing it live.

How do we migrate from the Zoom JWT app type to OAuth?

JWT app types are gone, and the migration path depends on how the integration is used. For server-only workflows, Server-to-Server OAuth is the replacement, with client credentials grants and one-hour access tokens that have to be refreshed. For integrations that act on behalf of users, the full OAuth 2.0 authorization code grant is required. In either case, scopes have to be chosen carefully and the token lifecycle has to be handled in code, not left as an afterthought.

Why does our Meeting SDK integration reject the JWT signature?

The Meeting SDK requires a JWT signed with the SDK Key and Secret from the SDK app type (not the Marketplace OAuth credentials), using HS256, with a specific set of claims including role, sdkKey and exp. The error messages are terse and point at the wrong place. We rebuild the signing on the server side (never in the browser), rotate the secret safely, and verify a test join before pushing to production.

How do we handle Zoom SSO certificate rotations without downtime?

By uploading the new certificate on the Zoom side in parallel with the rotation on the identity provider, verifying a test login against the new certificate before switching defaults, and keeping a documented rollback path. Most Zoom SSO outages we see are rotations that were planned on one side and not the other, or renewals that were scheduled for a weekend that happened to fall on a public holiday.

Can we embed Zoom meetings into our own product?

Yes, through the Meeting SDK (for a standard Zoom meeting UI inside your app) or the Video SDK (for a fully custom video experience using Zoom's media stack). Both require careful JWT signing, careful handling of the browser permission prompts, and a plan for licensing, since embedded sessions can count against your account's licenses depending on the mode. We build the server signing, the client integration, and the browser-permission UX together rather than piece by piece.

How much does Zoom help cost?

The estimate is free. Share the symptom, the app type (JWT, OAuth, SDK) and what is failing, and we come back with a scope and a fixed price before anyone touches the account.

Free estimate

Zoom giving you trouble?

Webhook signing, SSO configuration, JWT to OAuth migrations and Meeting SDK integrations. We work across the whole Zoom developer surface.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.