Server-to-Server OAuth

Setup
Reference

What You'll Need

Credential	What it is
Account ID	Zoom account identifier
Client ID	OAuth client ID
Client Secret	OAuth client secret

Overview

Connect Parable to Zoom for account users, meeting reports, and past meeting participants using Server-to-Server OAuth. Parable obtains access tokens with only Account ID, Client ID, and Client Secret — no end-user sign-in during sync.

Users

List and profile data for users in your Zoom account

Meetings & reports

Per-user meeting history reports where scopes allow

Meeting participants

Per-meeting participant identities for past meetings

Prerequisites

Setup access in . These steps require , or a colleague with equivalent permissions who can create credentials for you.If that is not you, ask your administrator.

Setup Guide

Access Zoom App Marketplace

Go to Zoom App Marketplace
Click Develop → Build App
Sign in with your Zoom admin account

Create Server-to-Server OAuth App

Find Server-to-Server OAuth in the app types
Click Create
Enter app name: Parable Integration
Click Create

Copy Credentials

On the App Credentials page, copy:

Account ID
Client ID
Client Secret

Store these credentials securely — the Client Secret cannot be retrieved later.

Add Scopes

Go to Scopes and add the following:

Scope	Purpose
`user:read:list_users:admin`	List account users
`report:read:user:admin`	Per-user meeting history reports
`meeting:read:list_past_participants:admin`	Past meeting participant lists

These are the current granular scope names required by the Zoom API. Older apps may show user:read:admin and report:read:admin — both still work but new apps should use the granular names above.

Activate the App

Complete all required fields (Information, Feature)
Go to Activation
Click Activate your app

The app will be activated immediately for your account.

Enter values in the form

Enter Account ID, Client ID, and Client Secret into the connector form, then click Save & test connection.

Verify Your Setup

curl -X POST "https://zoom.us/oauth/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -u "CLIENT_ID:CLIENT_SECRET" \
  -d "grant_type=account_credentials" \
  -d "account_id=ACCOUNT_ID"

Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.

Enter Account ID, Client ID, and Client Secret in the connector form, then click Save & test connection.

Rate Limits: enforces rate limits of .Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Troubleshooting

Error	Meaning	Solution
`124 Invalid access token`	Token expired/invalid	Regenerate access token
`200 Permission denied`	Missing scope	Add required scope and reactivate
`1001 User not found`	User doesn’t exist	Verify user email/ID
`429 Rate limit exceeded`	Too many requests	Implement backoff

Common Issues

App not returning data

Ensure the app is activated and all required scopes are added. Changes to scopes require reactivation.

Can’t see certain users

Server-to-Server OAuth apps have access to all users in the account. If users are missing, they may be in a different Zoom account.

Server-to-Server OAuth

What You'll Need

Overview

Users

Meetings & reports

Meeting participants

Prerequisites

Setup Guide

Verify Your Setup

Troubleshooting

App not returning data

Can’t see certain users

Additional Resources

Zoom REST API

S2S OAuth Guide

What You'll Need

​Overview

Users

Meetings & reports

Meeting participants

​Prerequisites

​Setup Guide

​Verify Your Setup

​Troubleshooting

​App not returning data

​Can’t see certain users

​Additional Resources

Zoom REST API

S2S OAuth Guide

Overview

Prerequisites

Setup Guide

Verify Your Setup

Troubleshooting

App not returning data

Can’t see certain users

Additional Resources