Integrations

Method	Path	Purpose
`GET`	`/api/v1/integrations`	List a tenant’s connected integrations
`GET`	`/api/v1/integrations/{integration_type}/oauth/authorize`	Start an OAuth flow (Google, WordPress.com, Slack)
`GET`	`/api/v1/integrations/oauth/callback`	OAuth provider redirects here
`POST`	`/api/v1/integrations/wordpress/connect`	Connect a self-hosted WordPress site via application password (no OAuth)
`POST`	`/api/v1/integrations/ahrefs/connect`	Connect an Ahrefs API subscription
`GET`/`PATCH`/`DELETE`	`/api/v1/integrations/{config_id}`	Manage one integration
`POST`	`/api/v1/integrations/{config_id}/sync`	Trigger an on-demand sync (GSC/GA4) outside the scheduled cadence

Two ways to connect WordPress

Most integrations (GSC, GA4, Slack, WordPress.com-hosted) go through OAuth. Self-hosted WordPress — the common case for client sites — uses an application password instead: POST /integrations/wordpress/connect with the site URL and an application password generated in that site’s wp-admin, no OAuth app registration needed per client site.

Webhooks

Method	Path	Purpose
`POST`	`/api/v1/webhooks/slack/actions`	Slack interactive-action callback (approval buttons)
`POST`	`/api/v1/webhooks/wordpress/{tenant_id}`	WordPress-side webhook receiver

Both verify their signature with a timing-safe comparison before processing — see Security.

API Reference

API Endpoints

Integrations

Two ways to connect WordPress

Webhooks

Integrations guide

​Two ways to connect WordPress

​Webhooks

Integrations guide

Two ways to connect WordPress

Webhooks