Keep custom providers outside the plugin

POM Translate does not publish a custom machine-translation endpoint contract. Do not copy an internal route, request body, response shape, or authentication implementation into a third-party integration.

When a project must use another provider, separate the responsibilities:

  • let the external system handle its own credentials, provider selection, retention, and billing;
  • exchange only approved source and translation values through POM Translate's supported import and export workflow;
  • preserve exact source matching and protected placeholders;
  • assign a supported translation status during import;
  • review the result in WordPress before publishing it.

This boundary prevents a provider integration from depending on private transport details that can change without becoming part of the public compatibility contract.

Do not call internal POM Translate classes from a cron job or write provider output directly to translation storage. That skips validation and can leave stale caches or translations attached to an outdated source value.

For recurring external work, build a controlled export–translate–review–import process. If live background translation is required, use the built-in POM AI workflow.

Let POM AI manage service authorization
Previous
Understand the single 404 redirect rule
Next