אינטegrations ו-API

Headless architecture

Traditional CMS platforms couple content management with frontend rendering. Whoopix separates these layers completely:

This architecture is detailed on the Architecture page and enables the integration flexibility described on Integrations.

REST API

The Whoopix REST API provides read and write access to content, products, and SEO data:

All responses include SEO metadata, schema data, and language variants where applicable. Authentication uses API keys configured in the admin panel under Settings > Integrations.

Webhooks & events

Whoopix can push events to external systems when content changes:

• page.published — trigger CDN cache purge, search index update, or notification
• article.published — push to email newsletter, social media, or RSS
• product.updated — sync inventory to ERP or marketplace
• order.created — notify fulfillment system or CRM
• serp.changed — alert team when keyword rankings shift significantly

Configure webhook URLs and event subscriptions in the admin panel. Payloads are JSON with full entity data.

Direct database access

Unlike SaaS CMS platforms, Whoopix runs on your database. Developers have direct MySQL access for custom queries, reporting, and sync logic:

Direct database access eliminates middleware layers and reduces integration timelines from months to weeks. Your team owns the data — no export restrictions or vendor lock-in.

Common integrations

Teams commonly connect Whoopix to:

Insights module — analytics data and integration monitoring.

Developer workflow

1. Generate API keys in Settings > Integrations
2. Test endpoints with curl or Postman using your key
3. Build frontend components that consume the JSON responses
4. Configure webhooks for real-time sync on content changes
5. Set up staging environment for testing before production deploy

For developer-focused positioning, see SEO AI For Developers.