Ops Lab Playbook: Site Runtime Ops

Last updated: 2026-03-08

1. Purpose and when to use this

Use this module to create site deployments, preview deployment output, and change site mode safely.

2. User roles and auth modes

• JWT creator: deployment create and preview.
• JWT owner: site mode updates.

3. Prerequisites checklist

• Primer completed: Onboarding and API Primer
• Handle has site/profile configuration.
• JWT_TOKEN with creator/owner role depending on action.
• Deployment payload includes a root index.html file. Without this, deployment activation fails with missing_entrypoint.

4. UI onboarding flow

1. Open https://app.10x.in/creator/site-runtime.
2. Create a deployment and capture deployment ID.
3. Request deployment preview.
4. Update site mode if needed.

5. API workflow map

1. SR-01: POST /v2/handles/{handle}/site-deployments
2. SR-02: GET /v2/handles/{handle}/site-deployments/{deploymentId}/preview
3. SR-03: PUT /v2/handles/{handle}/site-mode

6. cURL examples

Set module variables:

export DEPLOYMENT_ID="<deployment-id>"

SR-01 Create deployment

curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/site-deployments" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{"note":"creator deploy"}'

SR-02 Preview deployment

curl -sS "${API_BASE}/v2/handles/${HANDLE}/site-deployments/${DEPLOYMENT_ID}/preview" \
  -H "authorization: Bearer ${JWT_TOKEN}"

SR-03 Update site mode

curl -sS -X PUT "${API_BASE}/v2/handles/${HANDLE}/site-mode" \
  -H "authorization: Bearer ${JWT_TOKEN}" \
  -H 'content-type: application/json' \
  -d '{"mode":"LINKTREE"}'

7. Expected success outputs and verification checks

• Deployment create returns 201 with deployment identifier and upload URLs.
• Preview returns a signed previewUrl (temporary access link to deployment index.html).
• Do not use raw S3 object URLs for preview checks; bucket objects are not public.
• Site mode update returns persisted mode confirmation.

8. Failure modes and remediation

• 403 on site mode update:
• Remediation: use owner JWT for mode change.
• Preview not available yet:
• Remediation: wait for deployment processing completion and retry.
• 400 missing_entrypoint on deploy activation:
• Remediation: include root index.html in deployment files.
• 409 deployment_entrypoint_missing on preview:
• Remediation: ensure deployment index.html exists (or active deployment has live profiles/{handle}/index.html fallback).
• 404 deployment ID errors:
• Remediation: confirm deployment ID belongs to current handle.

9. Async behavior notes

• Deployment draft creation and preview URL issuance are synchronous API actions.
• File upload is client-driven via presigned PUT URLs.
• Activation copies uploaded files into the live profiles/{handle}/ prefix and then marks deployment active.

10. Related links

• QA Automation Console
• Creator Revenue