---
id: TST-PFM-INT-176
title: Zoom tokens are refreshed before they expire and a webinar is created on a fresh token
kind: api-lifecycle
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - acceptance/integrations/playwright/journeys/credentials/INT-ACC-0178.spec.ts
implements: []
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
isolation: >-
  Use the acceptance harness workspace restrictions, persona fixtures, run-marked records and cleanup;
  exclusive or destructive cases require the disposable workspace.
evidence:
  - 'react-console:acceptance/integrations/playwright/journeys/credentials/INT-ACC-0178.spec.ts'
test_cases: []
acceptance_record: acceptance/integrations/journeys/credentials/INT-ACC-0178.json
execution_modes:
  - deployed-dev
  - mock
harness_limitations: >-
  The wrapper can block or set aside a journey according to its acceptance record and approved exclusion
  register.
recorded_isolation: parallel-safe
recorded_automation:
  status: blocked
  isolation: parallel-safe
  blocked_reason: 'rewrite pending (INTG-M4): Needs OAuth sign-in on the Dummy''s branch agent/ip-dummy-oauth-async.'
---
# Zoom tokens are refreshed before they expire and a webinar is created on a fresh token

## Verification Boundary

This API journey suite exercises the acceptance journey for zoom tokens are refreshed before they expire and a webinar is created on a fresh token. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

## What It Does Not Prove

A mock run does not establish deployed persistence, provider effects or service authorization. The suite does not establish a complete feature sequence merely because it visits several screens.

## Real Dependencies and Test Doubles

The deployed mode uses the acceptance service clients and reads resulting records. The mock mode substitutes service responses through the harness; neither mode requires a browser interaction in this file.

## Must Not Be Doubled

The service operations and resulting-record assertions for a claimed API outcome must execute. A deployed claim requires the actual persistence effects checked by that step.