Flx Headless renders published WordPress Pages, single Posts, the blog index, category
archives, tag archives, search results, and the 404 page through an external
Flx Render service instead of WordPress’s native template output. If the
Render service is unreachable, returns an error, or a required field is
missing from the payload, Flx Headless falls back to normal WordPress rendering, so
visitors always see a page.
Each route rendered through Flx Headless includes a page title, meta description,
canonical URL, and robots directive where applicable.
Flx Headless also provides:
/wp-json/flx-headless/v1/health./wp-json/flx-headless/v1/global-styles servingMenus, comments, and full-site rendering are not covered.
Flx Headless renders Pages, Posts, the blog index, category and tag archives, search
results, and the 404 page by sending page data to an external Flx Render
service over HTTPS and displaying the HTML it returns. This is required for
Flx Headless to function as a headless rendering integration.
No data is sent anywhere until an administrator configures a Render URL —
either by entering one on the Flx Headless screen and saving it, or with
one click via the dismissible setup notice shown in wp-admin after
activation. Before a Render URL is configured, Flx Headless performs no external
requests and falls back to normal WordPress rendering.
The Render URL is entirely administrator-controlled. It may point to any
service that implements the Flx Render API, including a self-hosted instance;
Flx Headless does not require use of any specific provider.
For each request that Flx Headless renders through the configured service, the
following data is sent, depending on the content being rendered:
No WordPress user account data, credentials, email addresses, or license
keys are transmitted to the Render service.