links.10x.in/docs/end-user/playbooks/ops-lab-revenue-ops Published:

Ops Lab Playbook: Revenue Ops

Last updated: 2026-03-08

1. Purpose and when to use this

Use this module for owner-level monetization operations: connect onboarding, connect status checks, earnings monitoring, and group-buy publication.

2. User roles and auth modes

  • JWT owner: connect onboarding/status and earnings reads.
  • JWT operator: group-buy publish.

3. Prerequisites checklist

  • Primer completed: Onboarding and API Primer
  • Billing/connect integration configured for environment.
  • JWT_TOKEN with required owner/operator role.

4. UI onboarding flow

  1. Open https://app.10x.in/creator/revenue-ops.
  2. Start connect onboarding.
  3. Verify connect status.
  4. Read earnings snapshot.
  5. Publish active group-buy.

5. API workflow map

  1. RO-01: POST /v2/handles/{handle}/connect/onboarding
  2. RO-02: GET /v2/handles/{handle}/connect/status
  3. RO-03: GET /v2/handles/{handle}/earnings
  4. RO-04: POST /v2/handles/{handle}/group-buys/{groupBuySlug}/publish

6. cURL examples

Set module variables:

export GROUPBUY_SLUG="vip-launch"

RO-01 Start connect onboarding

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/connect/onboarding" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{}'

RO-02 Read connect status

curl -sS "${API_BASE}/v2/handles/${HANDLE}/connect/status" \
  -H "authorization: Bearer ${JWT_TOKEN}"

RO-03 Read earnings

curl -sS "${API_BASE}/v2/handles/${HANDLE}/earnings" \
  -H "authorization: Bearer ${JWT_TOKEN}"

RO-04 Publish group-buy

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/group-buys/${GROUPBUY_SLUG}/publish" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{}'

7. Expected success outputs and verification checks

  • Connect onboarding returns onboarding URL/session metadata.
  • Connect status reflects readiness flags.
  • Earnings endpoint returns aggregate totals.
  • Group-buy publish response indicates published availability.

8. Failure modes and remediation

  • 403 on connect routes:
  • Remediation: ensure owner JWT (not creator-only role).
  • Earnings empty despite known activity:
  • Remediation: wait for rollup completion and verify webhook processing.
  • Group-buy publish blocked:
  • Remediation: confirm group-buy exists and required preconditions are met.

9. Async behavior notes

  • Connect setup/status endpoints are synchronous contract paths.
  • Group-buy publication may emit downstream rollup events via background processing.

10. Related links