Integrate Deepglot

Quickstart

1. 1.Create an account and a dashboard project with source and target languages.
2. 2.Create a project API key. Its plaintext is shown once and must not be embedded in browser code.
3. 3.Install the WordPress plugin, enter the API URL and key, and run the connection test.
4. 4.Open a translated URL and verify navigation, hreflang, cache, dynamic content, and quota status.

API reference

curl https://deepglot.ai/api/translate \
  -H "Authorization: Bearer dg_live_…" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 9b9e42d8-7ef2-4a91-82ff-b5ec71ba5832" \
  -d '{
    "l_from": "de",
    "l_to": "en",
    "words": [{ "w": "Hallo Welt", "t": 1 }],
    "request_url": "https://example.com/",
    "bot": 0
  }'

{
  "l_from": "de",
  "l_to": "en",
  "request_url": "https://example.com/",
  "title": "",
  "bot": 0,
  "cache_only": false,
  "from_words": ["Hallo Welt"],
  "to_words": ["Hello world"]
}

HTTP/1.1 200 OK

// Database unavailable: HTTP 503 with a service_unavailable Problem Details body.

[
  {
    "code": "de",
    "local_name": "Deutsch",
    "english_name": "German",
    "sharedAcrossProviders": true
  }
]

{ "is_supported": true }

{
  "exclusions": { "urls": [], "regexes": [], "selectors": [] },
  "pageViewsEnabled": false,
  "project": {
    "version": "2026-08-25T10:00:00.000Z",
    "name": "Example website",
    "domain": "example.com",
    "sourceLanguage": "de",
    "targetLanguages": ["en"],
    "autoRedirect": false,
    "displayAiNotice": true,
    "automaticTranslation": true,
    "websiteType": "Corporate website",
    "industryType": "Software & technology"
  },
  "urlSlugs": [
    { "originalSlug": "ueber-uns", "translatedSlug": "about-us", "langTo": "en" }
  ],
  "syncedAt": "2026-07-13T10:00:00.000Z"
}

{
  "routingMode": "PATH_PREFIX",
  "siteUrl": "https://example.com",
  "sourceLanguage": "de",
  "targetLanguages": ["en"],
  "autoRedirect": false,
  "translateEmails": false,
  "translateSearch": true,
  "translateAmp": false,
  "domainMappings": []
}

{
  "ok": true,
  "project": {
    "id": "project-id",
    "name": "Example website",
    "domain": "example.com",
    "originalLang": "de",
    "languages": [{ "langCode": "en", "isActive": true }]
  },
  "mirrorConflicts": ["domain", "autoRedirect"]
}

WordPress

Plugin REST routes run on the WordPress site and require WordPress administrator permissions. Dynamic translation uses a nonce, short-lived word ticket, per-IP budget, and the server-side organization cap. Missing authorization degrades to cache-only behavior; bots never trigger fresh translation.

A Universal JavaScript snippet and reverse proxy are not currently available. WordPress is the only supported integration path.

AMP pages enter the translation pipeline only when the plugin option is enabled. The multilingual sitemap at /deepglot-sitemap.xml is advertised in robots.txt and contains only validated internal language alternatives.

From version 0.12.0, an ordinary page request does not wait for fresh translations by default. Missing segments enter a bounded, deduplicated queue and are translated by WP-Cron. If a cold request cannot store both its text and cache target because the short queue lock is busy, its source-language response is not cached and a later request can retry. The visual editor and WooCommerce emails remain synchronous because those outputs cannot converge automatically on a later request.

Administrators can start a bounded URL synchronization from the Deepglot sitemap under Settings → Deepglot. A side-effect-free preview with an immutable snapshot and sample URLs must be confirmed before it starts. When WordPress recognizes a safe HTTPS request on the same host as an internal target still stored with HTTP, the snapshot uses the same internal target with HTTPS. Semantic query parameters and fragments are preserved. A foreign request host is never copied. One absolute, query- and fragment-free redirect on the exact same origin and in the requested target language is verified explicitly through separate public and origin probes; automatic redirect following remains disabled. Other redirects remain bounded failures. Each batch contains at most 250 target pages, feeds the same translation queue at a controlled rate, and can be paused, resumed, or cancelled. It is not a permanent background crawler.

• GET /wp-json/deepglot/v1/settings
• PUT /wp-json/deepglot/v1/settings
• PATCH /wp-json/deepglot/v1/settings
• GET /wp-json/deepglot/v1/status
• POST /wp-json/deepglot/v1/test-connection
• GET /wp-json/deepglot/v1/url-sync
• POST /wp-json/deepglot/v1/url-sync/preview
• POST /wp-json/deepglot/v1/url-sync
• POST /wp-json/deepglot/v1/url-sync/pause
• POST /wp-json/deepglot/v1/url-sync/resume
• POST /wp-json/deepglot/v1/url-sync/retry-failed
• DELETE /wp-json/deepglot/v1/url-sync
• POST /wp-json/deepglot/v1/translate-dynamic

WordPress operations help

The first request for a page without cached translations can intentionally show source content. It places missing segments in the warm-up queue, and an immediately due WP-Cron event processes them in the background. Once the queue and event are stored, Deepglot makes one non-blocking WP-Cron nudge per request. That nudge is skipped for DISABLE_WP_CRON and while cron is already running. After success, Deepglot purges affected pages from supported full-page caches so the next request receives the locally cached translation.

Only translation 429 responses set the active marker. The marker and warmer backoff are bound to the API key and backend; configuration changes, late responses from the previous configuration, and legacy or unbound markers do not block new translations.

When every attempted provider reports only a count mismatch for the same multi-text root chunk, Deepglot starts direct singleton isolation. It skips redundant binary intermediate shapes and retries each original text through the configured provider chain in input order. The provider-call ceiling is chain length × (chunk size + 1) for a multi-text root, while an original singleton gets one chain; a default eight-text chunk with two providers therefore allows at most 18 provider calls. All root chunks and isolated singletons share the request-wide provider-call concurrency cap (default 12) and a provider-work deadline of at most 100 seconds. PDF translation uses a separate 40-second budget from route entry; authentication, multipart handling, and PDF preparation reduce the remaining provider time so the 60-second route nominally retains 20 seconds for completion work. A failing parallel chunk stops new sibling provider calls. Singleton, call-budget, and deadline mismatches remain terminal; timeouts, authentication failures, rate limits, U+0000, and other malformed responses never trigger these extra requests.

Deepglot finishes all bounded root-chunk attempts before starting singleton work. It collects only roots whose complete provider chains produced count mismatches; any other terminal error still aborts siblings immediately. Before calibration, Deepglot compares the remaining deadline with a conservative one-wave reserve: the fastest elapsed duration among the completed full count-mismatch root chains. If that reserve cannot fit, no singleton provider call starts. This root-derived reserve is used only for calibration admission and is never extrapolated across later work. It then runs exactly one global calibration wave containing the first min(request-wide concurrency, total mismatched texts) real singletons through their full provider fallback chains and retains its results. If the shared deadline expires during any admitted singleton wave despite the admission checks, Deepglot returns the same typed deadline error instead of a generic timeout. The remaining work is split into request-wide bounded waves. Before each later wave, Deepglot compares waves still pending × duration of the immediately preceding observed singleton wave with the remaining shared deadline and remeasures after every completed wave. That deadline is the earlier of the local provider-work ceiling and the caller's monotonic absolute deadline; the PDF route passes its route-entry 40-second deadline so authentication, upload handling, and preparation consume the same budget. If the pending work cannot fit, the request stops after the last retained wave and before any further singleton call. API and PDF return the stable 503 code ‘translation_count_mismatch_deadline’; once the first provider call starts, the API conservatively retains its velocity reservation and retains an idempotent same-key 503 for at most 60 seconds. Otherwise, the remaining affected texts continue through the same globally bounded singleton queue, preserving result order and each text's full provider fallback chain.

The localized public request URL remains the cache target even after the request router internally rewrites it to the source path.

Weekly workspace activity digest

The weekly digest is opt-in per user and workspace. The preference is stored in account settings; the PATCH route updates both the enabled state and the requested email locale.

Authoritative implementation: src/lib/activity-digest.ts, src/lib/activity-digest-delivery.ts, src/lib/activity-digest-cron.ts, src/components/einstellungen/activity-digest-preferences.tsx.

WordPress v0.11.4 through v0.11.7

The documented implementation history forms the basis for the current v0.12.8 implementation. v0.12.1 assigned a new public asset version to the Retry-After-aware dynamic translator. v0.12.2 verifies exactly one safe canonical redirect during URL synchronization without enabling automatic redirect following. v0.12.3 stores text and URL queues in a versioned, checksummed ASCII envelope so emoji and other four-byte Unicode remain durable on legacy WordPress option tables; damaged persistence is not silently replaced. v0.12.4 protects translated transient values with a separate versioned ASCII envelope. A failed cache write stays in both queues, prevents the page purge, and keeps a non-durable inline result out of the page cache. v0.12.5 translates explicitly configured consent widgets even when they render before the dynamic footer observer and localizes their internal links with server-side routing rules without sending URLs to a translation provider. v0.12.6 follows WordPress core post-type viewability: built-in public pages remain in the sitemap and URL synchronization, while non-viewable builder content types, attachments, and non-queryable taxonomies stay excluded. v0.12.7 synchronizes project-wide settings as a versioned SaaS snapshot. v0.12.8 translates generic ARIA labels, image tooltips, and human-readable RSS/Atom feed titles without sending ordinary link metadata to the translation provider, and rejects blank translation-cache values including legacy entries. A GitHub release or ZIP build does not automatically install a customer plugin; production installation and live QA remain separate approvals.

Errors and retries

Public and plugin routes use a Problem Details-style JSON contract. error remains as a legacy alias for existing plugin versions. Clients should branch on code and status; detail is human-readable.

A validation_failed response for U+0000 means a text, language, title, or request-URL field contains a NUL character that PostgreSQL cannot represent. Deepglot does not send that input to a provider or store it. Remove only U+0000 before retrying; other control characters and valid Unicode are supported.

Retryable 429 responses are not retained by Idempotency-Key beyond the bounded Retry-After window: concurrent same-key callers receive the same response, and the key may execute again after expiry. A 422 velocity_request_too_large is deterministic and retains the normal replay contract. Split an oversized request or PDF into smaller units.

{
  "type": "https://deepglot.ai/problems/validation-failed",
  "title": "Validation failed",
  "status": 400,
  "detail": "languageFrom and languageTo are required.",
  "code": "validation_failed",
  "instance": "/api/public/languages/is-supported",
  "error": "languageFrom and languageTo are required.",
  "errors": { "languageFrom": ["Required"], "languageTo": ["Required"] }
}

Webhooks

Project managers configure public HTTPS targets. Deepglot checks targets for SSRF at creation and dispatch, signs timestamp.payload with HMAC-SHA256, and sends X-Deepglot-Event, X-Deepglot-Timestamp, and X-Deepglot-Signature. Failed deliveries retry after 60, 300, and 900 seconds.

• translation.created
• translation.updated
• translation.manual_updated
• translation.deleted
• glossary.upserted
• glossary.deleted
• slug.upserted
• import.completed

Project surfaces

These routes power the dashboard and are not a stable external REST contract. API keys, languages, webhooks, exclusions, and the Pro+ translation-memory setting require management access. Human review and PDF translation are additionally project- and language-scoped. Managers may edit, delete, assign, and approve segments; translators may only edit and submit segments assigned to them in their language. Glossary CRUD currently uses the weaker project-membership gate. Import, export, and editor sessions use signed-in, project-specific access.

Languages, versioning, and support