Meeting connections
An account's Zoom and Webex connections, and the hosted flow that creates them.
Guides: Meetings.
| Method | Path | Operation | Scope |
|---|---|---|---|
GET | /v1/accounts/{accountId}/meeting-connections | List an account's meeting connections | read |
DELETE | /v1/accounts/{accountId}/meeting-connections/{service} | Remove a meeting connection | write |
POST | /v1/accounts/{accountId}/meeting-connect-sessions | Create a hosted meeting connect session | write |
Runs in your browser against api.workwae.com with the key you enter. Use a read-only key, limited to a test account if you can.
Required scope: read.
accountId*stringuuidOK
application/json- response
items*array<>curl -X GET 'https://api.workwae.com/v1/accounts/6f1c2a4e-8b3d-4e5f-9a7b-1c2d3e4f5a6b/meeting-connections'{ "items": [ { "service": "zoom", "email": "string", "displayName": "string", "meetingAppId": "de5403a8-6991-4374-9226-7c23a92df426", "status": "active", "statusReason": "string", "createdAt": "2026-05-04T09:30:00.000Z", "updatedAt": "2026-05-04T09:30:00.000Z" } ]}Runs against the live API with the key you enter: this change really happens. Use a key limited to a test account.
Deletes the grant (and revokes it at Zoom); meetings created with it stay. Later events use the tenant's server app, if any. Allowed without the meetings module, so a tenant can remove a grant it no longer uses.
Required scope: write.
accountId*stringuuidservice*string"zoom""webex"OK
application/json- response
curl -X DELETE 'https://api.workwae.com/v1/accounts/6f1c2a4e-8b3d-4e5f-9a7b-1c2d3e4f5a6b/meeting-connections/zoom'nullRuns against the live API with the key you enter: this change really happens. Use a key limited to a test account.
Returns a link to the hosted page where the account's user signs in to the service; the browser then returns to redirectUri with status=success|error, service, error and state, or without redirectUri to Workwae's own confirmation page, which needs no allowlist entry. The sign-in passes a Continue page on the API origin naming the tenant, the service and the account, and must finish in the browser that pressed Continue (an HttpOnly cookie on the API origin); a callback in any other browser renders an error page and connects nothing. A session yields at most one grant: once one sign-in completed it, the others end with error=session_used, and one completing after expiresAt ends with error=session_expired. Connecting again replaces the account's grant for the service.
Required scope: write.
accountId*stringuuidapplication/json- body
service*MeetingService"zoom""webex"redirectUri?stringurimeetingAppId?stringuuidstate?stringlength <= 1024ttlSeconds?integer60 <= value <= 864003600OK
application/json- response
id*stringuuidurl*stringuriexpiresAt*stringdate-timecurl -X POST 'https://api.workwae.com/v1/accounts/6f1c2a4e-8b3d-4e5f-9a7b-1c2d3e4f5a6b/meeting-connect-sessions' \ -H 'Content-Type: application/json' \ -d '{ "service": "zoom"}'{ "id": "c4e6a8b0-1d3f-4a5c-8e7b-9d1f3a5c7e9b", "url": "https://app.example.com/", "expiresAt": "2026-05-04T09:30:00.000Z"}