Workflow

Owner-driven agency relationship reactivation (disabled by default)

Follow the sequence below, then use API Reference for payload schema and response details.

Steps

  1. After a customer-paid relationship interval has ended—including an administrative removal at

    Operation IDs: agencyRelationships.reactivate

  2. Treat a conflict during delinquency as retryable after ordinary provider-authoritative billing

Notes

This workflow remains unavailable while agency attribution is disabled. It never runs from login,

a provider event, or billing recovery.

the exact interval start, which leaves no zero-length ended prefix—let only the current

customer workspace owner submit a fresh intent for the same approved agency code. The

reactivation requires a current paid provider subscription and the same approved agency; an

arbitrary agency or stale intent is rejected. Send a fresh `Idempotency-Key`:

recovery. The backend fetches the provider-current subscription and CAS-fences the local billing

projection before appending one new relationship interval. Historical removal evidence remains

audited at the exact start boundary; reactivation does not restore an arbitrary or unapproved

agency.

Related Docs

All workflowsAPI reference