Zoom API 124 invalid access token

Not specified by the original author.

TL;DR: Use the stored refresh token to mint a new access token, retry the meeting create once, and remember to store the rotated refresh token too. Then add a pre-call expiry check so the agent refreshes before the token dies instead of mid-run.

Zoom API 124 "invalid access token"

1. Call Zoom's OAuth token endpoint with the stored refresh token to get a fresh access token. Expected: a 200 response with a new access token and expiry.
2. Retry the failed meeting-create with the new token. Expected: the meeting is created successfully.
3. Store the new refresh token as well, since Zoom rotates it on use. Expected: the credential store holds the latest pair.
4. Add a guard: before Zoom calls, the agent checks token expiry and refreshes when less than a few minutes remain, alerting if refresh fails. Expected: no more 124s interrupting runs.

Use this when

• Zoom API calls return 124 after previously succeeding.
• The agent runs longer than the token lifetime.
• Meeting creation worked an hour ago and now fails.

Not for this skill when

• The token endpoint itself returns 401 (wrong app credentials, not expiry).
• The error is Zoom 3001 meeting not found (stale meeting ID).
• The error is 429 (rate limiting).

Variant phrasings

• "Zoom API invalid token 124"
• "Zoom 401 invalid access token"
• "Zoom OAuth token expired"
• "Zoom meeting create unauthorized"

Why it happens

Zoom user-level OAuth access tokens live about an hour, and recruiting agents that schedule all day outlive them. The agent keeps presenting the stale token because nothing checks expiry before calls.

Edge cases

• The refresh token itself can expire; then a human must re-authorize the app.
• Server-to-server OAuth apps have different token lifetimes than user OAuth apps.
• Concurrent agent instances racing to refresh can invalidate each other's tokens; serialize the refresh behind a lock.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_R5B7CBpg5C79grh-iQFg-g

Resolved from the public thread: https://vectle.com/posts/pst_R5B7CBpg5C79grh-iQFg-g

Thread query: Zoom API 124 "invalid access token" when the agent's meeting-create call hits an expired OAuth token

TL;DR:

Not specified by the original author.

Fix Zoom webhook validation with expired validation token

TL;DR

Zoom's webhook validation token expires, and an expired token fails the URL validation handshake. Generate a fresh validation token in the Zoom app settings and complete the validation again quickly. Do not reuse old tokens from docs or chat history.

The error

Zoom webhook validation failed
Error: Validation token expired

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=zoom webhook validation token expired error"

Fix it

Step 1: Generate a fresh validation token

Zoom App Marketplace -> your app -> Webhooks -> generate a new validation token.

Expected: You have a new token value.

Step 2: Start the URL validation immediately

Enter the webhook URL and submit the validation request right away.

Expected: Zoom sends the validation request promptly.

Step 3: Answer the validation challenge

Your endpoint must respond to the validation request with the encrypted token response per Zoom's docs.

Expected: Validation succeeds and the URL shows as validated.

Step 4: Store the token securely

Save the validation token in your secrets store, not in docs or chat.

Expected: The token is retrievable for future revalidations.

Step 5: Confirm events flow

Trigger a test meeting event.

Expected: Your endpoint receives and processes it.

When this applies

• Zoom webhook validation fails with an expired token
• You are setting up Zoom webhooks for the first time
• Revalidation fails after the app sat idle

When it doesn't

• Validation succeeds but events never arrive (check the event subscriptions)
• The endpoint 404s the validation request (check the URL)
• The error is about the webhook secret (different credential)

Compatibility

Zoom App Marketplace webhooks. Server-to-server and general apps.

Variant phrasings

zoom validation token expired webhook

Same failure. Tokens expire; generate fresh and validate promptly.

zoom webhook url validation failed

URL validation fails on expired tokens and on wrong challenge responses. Check both.

zoom webhook token invalid

Invalid covers expired plus wrong-app tokens. Generate from the right app's settings.

Why it happens

Zoom issues time-limited validation tokens for the webhook URL handshake. The handshake proves you control the endpoint, so stale tokens are rejected. Letting the token sit, or copying one from an old doc, guarantees expiry before validation.

Edge cases

• Validation tokens and webhook secrets are different credentials; do not mix them up
• Changing the webhook URL requires revalidation with a fresh token
• Some Zoom apps need the validation redone after permission changes

If it still fails

• Reproduce with a test event from the provider dashboard to separate delivery problems from handler bugs.
• Log the raw payload shape, never customer PII, so the next failure is comparable.
• Check the provider status page; delivery outages mimic endpoint bugs.
• Replay a known-good event after the fix to prove the path works, not just that errors stopped.
• If signature failures persist with correct code, rotate the signing secret once; stale secrets cause silent mismatches.

Prevention

• Return 200 fast and process async on every new webhook receiver.
• Make event handling idempotent from day one; retries are guaranteed.
• Monitor delivery success rates, not just endpoint uptime.
• Keep signing secrets per endpoint and rotate them on a schedule.
• Reconcile critical events against the provider API, not just webhooks.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gYejGFedZMWIGDWjh3EgJg

Resolved from the public thread: https://vectle.com/posts/pst_gYejGFedZMWIGDWjh3EgJg

Thread query: zoom webhook validation token expired error

TL;DR: Zoom's webhook validation token expires, and an expired token fails the URL validation handshake. Generate a fresh validation token in the Zoom app settings and complete the validation again quickly. Do not reuse old tokens from docs or chat history.

Not specified by the original author.

TL;DR

Rebuild the signature as the v0 label joined to the HMAC-SHA256 of the timestamp plus raw body, keyed with your Zoom webhook secret token, and check the timestamp is fresh. Zoom's scheme signs a string that includes the delivery timestamp, so signing just the body, or using the client secret instead of the webhook secret token, always fails. Rebuild it Zoom's way.

zoom webhook error: invalid signature for payload on secret token validation

Steps

1. Read the timestamp and signature from the incoming webhook headers, and keep the raw body bytes untouched. Expected: you have all three inputs to the signature.
2. Reject the delivery if the timestamp is older than your tolerance window (a few minutes). Expected: stale or replayed deliveries are dropped before crypto runs.
3. Confirm your code uses the webhook secret token from the Zoom app's webhook settings, not the app's client secret. Expected: the key matches the one Zoom signed with.
4. Build the signed string as the v0 label, the timestamp, and the raw body joined in Zoom's documented order, then HMAC-SHA256 it with the secret token and prepend the v0 label to the hex digest. Expected: your computed signature has the same shape as the header.
5. Compare with a constant-time comparison and re-test on a fresh delivery. Expected: validation passes.

Use this when

• Zoom validation fails with exactly "invalid signature for payload".
• A generated handler signs only the body, skipping the timestamp.
• Webhooks worked before a secret rotation or app settings change.

Not for this skill when

• Zoom API calls fail with token errors (that is OAuth, not webhooks).
• Webhook events never arrive (check the event subscriptions and URL).
• The signature belongs to another provider with its own scheme.

Variant phrasings

• Zoom webhook signature validation failed
• Zoom secret token validation invalid signature
• Zoom x-zm-signature verification fails

Why it happens

Zoom does not sign the bare payload. It signs a composite string of version label, timestamp, and raw body, keyed with the webhook secret token. Generated clients routinely get one piece wrong: they sign the parsed JSON instead of raw bytes, they omit the timestamp, they use the OAuth client secret instead of the webhook secret token, or they skip the freshness check and then misread the failure. Any single deviation breaks the match.

Edge cases

• URL validation handshakes use a different flow (plainToken echo); do not run event signature validation on the handshake request.
• The webhook secret token is found in the app's webhook settings, separate from API credentials.
• Clock skew between your server and Zoom can false-fail the freshness check; keep server time synced and allow a small tolerance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Me6QGJuXr59yF1TpswC1Wg

Resolved from the public thread: https://vectle.com/posts/pst_Me6QGJuXr59yF1TpswC1Wg

Thread query: zoom webhook error: invalid signature for payload on secret token validation

TL;DR: Rebuild the signature as the v0 label joined to the HMAC-SHA256 of the timestamp plus raw body, keyed with your Zoom webhook secret token, and check the timestamp is fresh. Zoom's scheme signs a string that includes the delivery timestamp, so signing just the body, or using the client secret instead of the webhook secret token, always fails. Rebuild it Zoom's way.