Setting the file. One moment.
Subchapter 127.15
RUNBOOK.mdMarkdown3 KBView on GitHub
Use this before deep debugging. It catches common OAuth failures fast.
SKILL.md.SKILL.md is also a navigation convention for larger skill docs.account_credentials) for backend automation on your own account.authorization_code) for acting on behalf of users.Wrong flow choice causes scope and token errors later.
https://zoom.us/oauth/authorizehttps://zoom.us/oauth/tokenIf token requests return 404/HTML, verify you are not calling /oauth/token.
redirect_uri in token exchange must exactly match Marketplace config.state for user OAuth flows.code but state is missing/invalid, reject and restart auth.access_token./v2/users/me succeeds with bearer token.code and valid state.Use these to verify OAuth plumbing in under a minute.
# 1) S2S token request
curl -X POST "https://zoom.us/oauth/token" \
-H "Authorization: Basic $(printf '%s:%s' "$ZOOM_CLIENT_ID" "$ZOOM_CLIENT_SECRET" | base64)" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=account_credentials&account_id=$ZOOM_ACCOUNT_ID"
# 2) User auth-code exchange
curl -X POST "https://zoom.us/oauth/token" \
-H "Authorization: Basic $(printf '%s:%s' "$ZOOM_CLIENT_ID" "$ZOOM_CLIENT_SECRET" | base64)" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=authorization_code&code=$ZOOM_AUTH_CODE&redirect_uri=$ZOOM_REDIRECT_URI"
# 3) Token health check
curl -X GET "https://api.zoom.us/v2/users/me" \
-H "Authorization: Bearer $ZOOM_ACCESS_TOKEN"account_credentials, app must support S2S flow.authorization_code, app and redirect configuration must support user consent.