Skip to content
HeadlessWP Pro

Integration guides

How to integrate common providers and verify capabilities.

Integration guides

HeadlessWP Pro supports multiple provider categories through extension-backed capabilities. Keep integrations capability-driven so the UI only enables flows available in the current environment.

Supported provider categories (high level)

  • WooCommerce for catalog, cart, checkout, and commerce account flows.
  • AffiliateWP for partner signup, tracking, referrals, and affiliate reporting workflows.
  • Restrict Content Pro for membership and entitlement-oriented account experiences.
  • FluentBooking for booking availability, reservations, and booking management flows.

Treat these as capability groups, not assumptions. A provider can be unavailable in a given environment even when code paths exist.

How to verify capabilities

Before enabling provider-specific UX, query:

  • GET /wp-json/headlesswp/v1/capabilities

Use the response to gate features and avoid hard-coding assumptions about provider availability.

Integration pattern guidance

  • Keep service-account credentials server-side only.
  • For browser logged-in UX, use cookie sessions and required nonce headers through the secure proxy boundary.
  • Route browser traffic through same-origin Next.js handlers rather than direct cross-origin calls.
  • Normalize and surface correlation IDs in logs and support tooling for faster incident triage.

Where to look next