{"id":318466,"date":"2026-06-13T00:37:46","date_gmt":"2026-06-13T00:37:46","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/polyglot-translate-connector\/"},"modified":"2026-06-13T00:37:21","modified_gmt":"2026-06-13T00:37:21","slug":"polyglot-translate-connector","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/polyglot-translate-connector\/","author":23474519,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.0","requires":"7.0","requires_php":"7.4","requires_plugins":null,"header_name":"Polyglot Translate Connector","header_author":"Elevio Solutions","header_description":"Polyglot Translate as a native WordPress 7.0 Connector. Self-learning translation API for 90+ languages, secure credential management, ready for any plugin.","assets_banners_color":"","last_updated":"2026-06-13 00:37:21","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/polyglot-translate.cloud\/wordpress-connector","header_author_uri":"https:\/\/polyglot-translate.cloud","rating":0,"author_block_rating":0,"active_installs":0,"downloads":35,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"polyglottranslate","date":"2026-06-13 00:37:21"}},"upgrade_notice":{"1.0.0":"<p>Initial public release.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3570657,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon-512x512.png":{"filename":"icon-512x512.png","revision":3570657,"resolution":"512x512","location":"assets","locale":"","width":512,"height":512}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Polyglot Translate card in the WordPress 7.0 Settings \u2192 Connectors screen, alongside Anthropic, OpenAI, and Google.","2":"Connected state \u2014 API key entered, validated against Polyglot Cloud, masked in the UI.","3":"Site Health debug info section showing connector metadata, key source, and last validation status.","4":"Advanced settings \u2014 optional custom API endpoint override for self-hosted or reverse-proxy deployments."}},"plugin_section":[],"plugin_tags":[220668,25308,99,2333,266900],"plugin_category":[48],"plugin_contributors":[266901],"plugin_business_model":[],"class_list":["post-318466","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-translation","plugin_tags-connector","plugin_tags-multilingual","plugin_tags-translation","plugin_tags-translation-api","plugin_category-language-tools","plugin_contributors-polyglottranslate","plugin_committers-polyglottranslate"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/polyglot-translate-connector\/assets\/icon-256x256.png?rev=3570657","icon_2x":"https:\/\/ps.w.org\/polyglot-translate-connector\/assets\/icon-256x256.png?rev=3570657","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p><strong>Polyglot Translate Connector<\/strong> plugs the <a href=\"https:\/\/polyglot-translate.cloud\">Polyglot Translate<\/a> cloud into the brand-new <strong>WordPress 7.0 Connectors API<\/strong> \u2014 the same screen where you configure Anthropic, OpenAI, and Google. One API key, securely stored, available to every plugin on your site that needs translation.<\/p>\n\n<h4>Why this exists<\/h4>\n\n<p>WordPress 7.0 introduced a native way for plugins to share credentials for external services. Instead of every translation-aware plugin shipping its own settings page and asking you to paste the same key over and over, this connector lets you set it <strong>once<\/strong> in <strong>Settings \u2192 Connectors<\/strong> and have it just work everywhere.<\/p>\n\n<h4>What makes Polyglot Translate different<\/h4>\n\n<p>Polyglot is not \"another machine translation API.\" It's a <strong>translation memory that learns from every edit anyone makes on your site or across the network<\/strong>. Translations get better the more they're used \u2014 the system remembers good phrasings, learns your terminology, and progressively replaces machine output with verified high-quality results. You pay per character, not per call, and your translation memory belongs to you (cancel anytime \u2014 your data stays).<\/p>\n\n<h4>What this plugin actually does<\/h4>\n\n<ul>\n<li>Registers Polyglot Translate as a <code>translation<\/code>-type connector in the WordPress 7.0 Connectors registry.<\/li>\n<li>Adds the Polyglot card to <strong>Settings \u2192 Connectors<\/strong>, with a logo, description, \"Get your API key\" link, and credential field.<\/li>\n<li>Validates your API key against Polyglot Cloud on save (warns you, doesn't block, if the cloud is unreachable).<\/li>\n<li>Exposes 5 stable PHP helper functions (<code>polyglot_get_api_key()<\/code>, <code>polyglot_is_connected()<\/code>, <code>polyglot_get_api_base_url()<\/code>, etc.) that <strong>any other plugin on your site can use<\/strong> to consume Polyglot transparently.<\/li>\n<li>Adds a Site Health check so you can verify the connection state anytime.<\/li>\n<li>Supports environment variables and PHP constants for credentials \u2014 enterprise-friendly, no API keys in your database if your security policy forbids it.<\/li>\n<\/ul>\n\n<h4>What this plugin does NOT do<\/h4>\n\n<ul>\n<li>It does <strong>not<\/strong> translate content. It's a credential + discovery layer. For an end-to-end translation experience (front-end language switcher, glossary, post editor), install the main <a href=\"https:\/\/wordpress.org\/plugins\/polyglot-translate\/\">Polyglot Translate<\/a> plugin alongside this one.<\/li>\n<li>It does <strong>not<\/strong> add visible admin UI beyond the native Connectors screen and one small Advanced settings sub-page for endpoint overrides.<\/li>\n<li>It does <strong>not<\/strong> ship any AJAX handlers or REST endpoints of its own.<\/li>\n<\/ul>\n\n<h4>For plugin developers \u2014 discover Polyglot from your plugin<\/h4>\n\n<p>If you're building a WordPress plugin (AI content generator, SEO tool, WooCommerce extension, multilingual workflow\u2026) and you want to use Polyglot Cloud as your translation backend, you no longer need to ship your own settings UI or ask users for an API key. This connector handles credential discovery:<\/p>\n\n<pre><code>if ( function_exists( 'polyglot_is_connected' ) &amp;&amp; polyglot_is_connected() ) {\n    $api_key = polyglot_get_api_key();\n    $base_url = polyglot_get_api_base_url();\n    \/\/ Make REST calls against $base_url\/v1\/translate, etc.\n}\n<\/code><\/pre>\n\n<p>For higher-level conveniences (batching, retry policy, response DTOs), an official <code>polyglot\/wp-sdk<\/code> Composer package is planned as a separate library that wraps this connector. Until released, consume the Polyglot Cloud REST API directly using the helpers above.<\/p>\n\n<h4>Credential precedence<\/h4>\n\n<p>Highest to lowest:<\/p>\n\n<ol>\n<li><code>POLYGLOT_TRANSLATE_API_KEY<\/code> environment variable (set in your hosting panel)<\/li>\n<li><code>POLYGLOT_TRANSLATE_API_KEY<\/code> PHP constant (defined in <code>wp-config.php<\/code>)<\/li>\n<li>Database option (set via Settings \u2192 Connectors)<\/li>\n<\/ol>\n\n<h4>Advanced \u2014 custom API endpoint<\/h4>\n\n<p>If you operate a self-hosted Polyglot deployment, a reverse-proxy gateway (Cloudflare Workers, AWS Lambda\u2026), or a staging environment, you can override the API base URL via <strong>Settings \u2192 Polyglot Translate<\/strong>. HTTPS-only.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install via the Plugins screen, or upload <code>polyglot-translate-connector<\/code> to <code>\/wp-content\/plugins\/<\/code>.<\/li>\n<li>Activate the plugin.<\/li>\n<li>Go to <strong>Settings \u2192 Connectors<\/strong> and paste your Polyglot Translate API key (get one at <a href=\"https:\/\/app.polyglot-translate.cloud\">app.polyglot-translate.cloud<\/a>).<\/li>\n<li>Done. Any Polyglot-aware plugin on your site can now use the same key.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"what%20is%20polyglot%20translate%3F\"><h3>What is Polyglot Translate?<\/h3><\/dt>\n<dd><p>Polyglot Translate is a cloud translation service with self-learning translation memory. Unlike generic machine translation APIs, Polyglot remembers good translations across uses, learns your terminology, and progressively replaces machine output with higher-quality verified results. You pay per character, not per call.<\/p><\/dd>\n<dt id=\"do%20i%20need%20this%20plugin%20if%20i%20already%20use%20the%20main%20polyglot%20translate%20plugin%3F\"><h3>Do I need this plugin if I already use the main Polyglot Translate plugin?<\/h3><\/dt>\n<dd><p>No. The main plugin handles everything end-to-end. This connector is for two specific audiences: (a) WordPress 7.0+ users who want their Polyglot key to live in the native Connectors registry and be available to multiple plugins, and (b) developers and agencies building custom translation workflows on top of Polyglot Cloud.<\/p><\/dd>\n<dt id=\"how%20is%20this%20different%20from%20the%20anthropic%2C%20openai%2C%20or%20google%20connectors%20that%20ship%20with%20wordpress%207.0%3F\"><h3>How is this different from the Anthropic, OpenAI, or Google connectors that ship with WordPress 7.0?<\/h3><\/dt>\n<dd><p>Those connectors expose <strong>AI text generation<\/strong> providers \u2014 they're for plugins that want to generate or rewrite content. This connector exposes a dedicated <strong>translation<\/strong> provider \u2014 purpose-built for high-quality multilingual translation with translation memory. Different tool, different job.<\/p><\/dd>\n<dt id=\"will%20this%20plugin%20send%20translation%20requests%20to%20polyglot%3F\"><h3>Will this plugin send translation requests to Polyglot?<\/h3><\/dt>\n<dd><p>No. It performs exactly one type of network call: a <code>GET \/v1\/health<\/code> preflight check against Polyglot Cloud whenever you save your API key, to verify the key is valid. Nothing else.<\/p><\/dd>\n<dt id=\"is%20my%20api%20key%20visible%20to%20other%20plugins%20on%20the%20site%3F\"><h3>Is my API key visible to other plugins on the site?<\/h3><\/dt>\n<dd><p>Yes \u2014 by design. This is the same model WordPress core uses for all Connectors (Anthropic, OpenAI, Google, Akismet). Site settings are shared. If you need per-plugin scoping, generate a separate scoped key for each consumer in your Polyglot Dashboard.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20polyglot%20cloud%20is%20temporarily%20unreachable%20when%20i%20save%20my%20key%3F\"><h3>What happens if Polyglot Cloud is temporarily unreachable when I save my key?<\/h3><\/dt>\n<dd><p>The key is still saved. An admin notice will tell you validation could not complete, and the Site Health check will show \"Recommended \u2014 unreachable.\" You can re-test at any time from Site Health.<\/p><\/dd>\n<dt id=\"is%20this%20affiliated%20with%20wordpress.org%20or%20automattic%3F\"><h3>Is this affiliated with WordPress.org or Automattic?<\/h3><\/dt>\n<dd><p>No. WordPress and the WordPress logo are trademarks of the WordPress Foundation. This plugin is developed by Elevio Solutions, the company behind Polyglot Translate.<\/p><\/dd>\n<dt id=\"can%20i%20use%20a%20custom%20api%20endpoint%3F\"><h3>Can I use a custom API endpoint?<\/h3><\/dt>\n<dd><p>Yes. Open <strong>Settings \u2192 Polyglot Translate<\/strong> and enter an HTTPS URL. Useful for self-hosted deployments, reverse proxies, or staging environments.<\/p><\/dd>\n<dt id=\"does%20this%20plugin%20send%20any%20data%20to%20third%20parties%3F\"><h3>Does this plugin send any data to third parties?<\/h3><\/dt>\n<dd><p>The only outbound call this plugin makes is <code>GET \/v1\/health<\/code> to Polyglot Cloud (<code>api.polyglot-translate.cloud<\/code>), with your API key in the <code>Authorization<\/code> header \u2014 used solely to validate the key on save. No telemetry, no analytics, no other endpoints. See our <a href=\"https:\/\/polyglot-translate.cloud\/privacy\">privacy policy<\/a> for what Polyglot Cloud itself does with translation traffic.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0 \u2014 2026-05-24<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<li>Registers Polyglot Translate as a <code>translation<\/code>-type connector in the WordPress 7.0 Connectors API.<\/li>\n<li>Preflight API key validation via <code>GET \/v1\/health<\/code> (warn-don't-block strategy).<\/li>\n<li>Public helpers for plugin developers: <code>polyglot_get_api_key()<\/code>, <code>polyglot_get_api_base_url()<\/code>, <code>polyglot_is_connected()<\/code>, <code>polyglot_get_connector_id()<\/code>, <code>polyglot_get_api_key_source()<\/code>.<\/li>\n<li>Site Health check integration (top-level test + debug info section).<\/li>\n<li>Secure credential management via Settings \u2192 Connectors (with environment variable + PHP constant overrides for enterprise hosting).<\/li>\n<li>Optional custom API endpoint override via Settings \u2192 Polyglot Translate.<\/li>\n<li>Localization-ready: English source, Serbian (sr_RS) translation included.<\/li>\n<\/ul>","raw_excerpt":"Self-learning translation API for WordPress 7.0+. 90+ languages, native Connectors integration, secure credential management, any-plugin ready.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/318466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=318466"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/polyglottranslate"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=318466"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=318466"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=318466"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=318466"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=318466"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=318466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}