Pipeline

Translation Pipeline

Understand how crawl, translate, render, and serving fit together.

Every rollout follows the same deterministic flow so you can re-run safely and track status.

Pipeline stages

Crawl source content
- POST /api/sites/{siteId}/crawl (sites.crawl.trigger)
- Optional selected-pages flow: POST /api/sites/{siteId}/crawl-translate (sites.crawl_translate.trigger)
Translate snapshots
- POST /api/sites/{siteId}/translate (sites.translate)
Render and publish
- Artifacts are rendered and deployed per locale.
Serve from edge
- Localized: GET /{path}
- Previews: GET /_preview/{previewId}

Check run status:
- GET /api/sites/{siteId}/translation-runs/{runId} (sites.translationRuns.get)
Pause or recover a run:
- POST /api/sites/{siteId}/translation-runs/{runId}/cancel (sites.translationRuns.cancel)
- POST /api/sites/{siteId}/translation-runs/{runId}/resume (sites.translationRuns.resume)
List pages and deployments:
- GET /api/sites/{siteId}/pages (sites.pages.list)
- GET /api/sites/{siteId}/deployments (sites.deployments.list)

Glossary:
- GET /api/sites/{siteId}/glossary (sites.glossary.get)
- PUT /api/sites/{siteId}/glossary (sites.glossary.put)
Overrides:
- POST /api/sites/{siteId}/overrides (sites.overrides.create)
Slugs:
- POST /api/sites/{siteId}/slugs (sites.slugs.set)

Locale summary frequency:
- PUT /api/sites/{siteId}/locales/{targetLang}/translation-summary (sites.locales.translationSummary.put)
Read range summaries:
- GET /api/sites/{siteId}/translation-summaries (sites.translationSummaries.list)

Crawl + translate selection:
- Uses the selected-pages endpoint documented above in Pipeline stages.
Account digest subscription:
- PUT /api/digests/subscription (digests.subscription.upsert)
Language switcher snippets:
- GET /api/sites/{siteId}/switcher-snippets (sites.switcherSnippets.get)