WordPress configuration

Dieser Leitfaden ist noch nicht in Ihre Sprache übersetzt.

After installing the plugin, you manage it from Settings → LegalCloud in your WordPress admin.

Settings

Connection

API token — the token you created in Organization → API. Required. Changing it re-validates the connection.
Environment — Auto (default), Production or Development. Leave it on Auto: the plugin uses the production API (https://api.legalcloud.info) and detects the right one for your token.

Defaults

Default language — used when a shortcode does not set lang (es, en, fr, de, it).

Wizard

The wizard (token → site → documents) opens when no token is configured. You can run it again from the settings page, and reset the plugin data if you want to start from scratch.

Overriding the API address

For special deployments (for example a proxy or a mirror) you can force the API address in wp-config.php, before activating the plugin:

define( 'LEGALCLOUD_WP_API_BASE_OVERRIDE', 'https://api.example.com' );

When it is defined it has priority over the environment setting. In normal installations do not define it.

Per-embed options

Everything else is configured per embed with the shortcode or the block arguments: hash (required), lang, height, mode and consent. See the shortcode reference.

Gutenberg blocks

The plugin registers a LegalCloud Document block and a LegalCloud Documents list block. To use them:

Edit a page or post and click +.
Search for "LegalCloud".
Choose the document, language, height and mode in the block sidebar.

With consent="1" an embed is not rendered until the visitor accepts cookies in the plugin's consent banner. Use it when your legal basis requires prior consent.

WP-CLI

wp legalcloud sync            # refresh organization, sites and documents
wp legalcloud sync --org
wp legalcloud sync --sites
wp legalcloud sync --docs

Useful in deployment pipelines to refresh the plugin cache.

REST endpoints of the plugin

The plugin exposes read endpoints under /wp-json/legalcloud/v1/ (organization, sites, documents) for the WordPress editor and for your own tooling. They require an authenticated WordPress user.

Multisite

The plugin is configured per site. In a Multisite network you can Network Activate it, but each subsite keeps its own settings and its own API token.

Next steps

Zuletzt aktualisiert: 2026-10-27