CMS integration

Parity can talk to your content platform so editors run accessibility checks where they already work, and publish events can queue targeted scans. You need a narrow CMS IntegrationAPI key, your site's Internal Site ID, and (for most setups) allowed scan domains configured in Parity before you install a connector on the CMS side.

Configure Parity first

In Parity, open Organization settings → API keys and create a key whose scopes include CMS Integration. Treat it like a secret — use env vars or your CMS secret store, not committed config files.
Open Site settings for the site you are connecting. Copy the Internal Site ID shown in the CMS integration helper for that site.
Still under site settings, set CMS integration: choose your platform, add allowed scan domains (staging or preview hostnames, one per line). Connectors can only ask Parity to scan URLs on those hosts plus your site's base URL — this limits what someone with a leaked key could request. Use connector-triggered actions there if you need to pause publish/update/delete handling from the CMS without changing CMS configuration.
Your API base URL is the origin of your Parity deployment (for example https://parity.example.com), with no trailing slash. WordPress and Symfony configs usually call this the Parity API base or similar.

Platform guides

Follow the guide for your CMS. Detailed connector contracts and troubleshooting for operators also live in the repository under cms-plugins/ and docs/specs/24-cms-integration.md.

Ibexa DXP (Symfony bundle)— coupled or headless, Composer install, env-based config.
WordPress plugin— upload ZIP, Settings → Parity Accessibility, block editor sidebar.
Drupal— roadmap; contact support if you need early access.

Network and security

Use HTTPS between your CMS, browsers, and Parity.
If staging sits behind a firewall or IP allowlist, add Parity worker egress addresses so crawlers can reach preview URLs. Your administrator can find current ranges in docs/STATIC-EGRESS-IPS.md in the Parity deployment repo, or contact Parity support.
CMS-scoped keys can call CMS-facing scan APIs and read findings for URLs you authorize — they cannot manage users, change org-wide settings, or mutate unrelated data.