Loading...
×
close
close

Integrations & API

Integrations & API

Whoopix is a headless CMS by design. Your team gets full API access, database ownership, and webhook support to connect any frontend, CRM, ERP, or third-party service.

Headless architecture

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

CMS (cms.whoopix.ai)

Content creation, SEO, admin, and data management.

API layer

REST endpoints serving structured JSON to any consumer.

Your frontend

PHP, React, Next.js, Vue, mobile apps — full presentation control.

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

Database → Whoopix Core → API / Direct Access → Your Frontend

REST API

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

Content endpoints: GET /api/pages — list pages (filter by status, template, language) GET /api/pages/{slug} — single page with content blocks and SEO data GET /api/articles — list articles with pagination GET /api/articles/{slug} — single article with full content GET /api/categories — category tree Product endpoints: GET /api/products — product catalog with filters GET /api/products/{slug} — single product with variants SEO endpoints: GET /api/sitemap — XML sitemap data GET /api/serp/{keyword} — ranking data for a keyword

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:

Common tables: mod_pages — page content and metadata mod_articles — blog/article content mod_products — product data mod_serp_keywords — tracked keywords mod_serp_positions — ranking history mod_schema_data — generated schema markup

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:

CRMs

HubSpot, Salesforce, Pipedrive — push leads from forms and orders.

Analytics

Google Analytics, Search Console, custom dashboards via API data.

Payment gateways

Stripe, PayPal, local payment providers for e-commerce.

Email marketing

Mailchimp, ActiveCampaign — sync subscribers and trigger campaigns.

CDN & caching

Cloudflare, Fastly — auto-purge on content publish via webhooks.

Custom frontends

Next.js, Gatsby, Nuxt — consume API for static or SSR sites.

Whoopix insights and analytics integration

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.

get in touch

We are always ready to help you and answer your questions

Get in touch with us to discuss your project, ask a question, or explore how we can work together.

Our Location

Israel, Tel Aviv - 701239
Ha'masger. 42

Social network

Get in Touch