🚧 Currently in alpha β€” stable release and Pro licensing coming in 2026. Star the repo to follow progress.

Skip to content

PRO

Settings Route ​

The /wp/v2/settings endpoint is a special WordPress REST route that exposes site-level configuration. Application Layer extends it with two additional data sources β€” ACF options pages and WordPress navigation menus β€” and applies the same schema editing tools available in the Properties & Models panel.

This makes /wp/v2/settings a convenient single endpoint for front-ends that need global site data: navigation, options, and configuration in one request, shaped to your schema.


Additional Properties ​

Beyond the standard WordPress settings fields, the following can be pulled into the response:

ACF Options Pages ​

A single option lets you include all registered ACF options pages as top-level properties. When enabled, every options page is added in full. In Pro, use the per-property control or custom schema to narrow down or restructure the data you want to expose.

Resolved WordPress Menus ​

Registered WordPress navigation menus can be included as a top-level property. Each menu is resolved to its full item tree β€” including labels, URLs, target, and nested children β€” rather than returning raw menu IDs.


Schema Editing ​

The schema editor for the settings route works identically to the one described in Properties & Models.

WordPress Schema

Applies the standard /wp/v2/settings response with optional transforms layered on top:

  • Relative URLs β€” strips the domain from URL fields
  • Resolve rendered props β€” unwraps rendered wrappers
  • Remove empty props PRO β€” strips null and empty string fields
  • Remove _links β€” removes the HAL links object
Per-Property Control PRO

Each individual property in the response can be managed at field level:

  • Disable β€” remove a specific property from the response
  • Rename β€” expose a property under a different key
  • Remap β€” source a property's value from a different field in the original response
Custom Schema PRO

Replaces the full response with a hand-crafted property map. Define each top-level key and map it to a dot-path from the original response. Properties support the following per-property transforms:

  • Resolve media β€” replace an attachment ID with the full media object. Uses the active model for attachment if defined, otherwise falls back to the default WP REST response.
  • Filter URL β€” strip the domain from URL fields (relative URLs)
  • Search & replace (under development) β€” apply text substitutions to string field values
Test

The Test tab fetches the live /wp/v2/settings response and displays the raw output alongside the transformed result side by side. Verify your schema before publishing β€” no external request needed.


Entry type: Model (Settings route)


FAQ ​

Is this route available in the free tier?

The route explorer lets you inspect the /wp/v2/settings schema in the free tier. Schema editing (per-property control, custom schema, ACF options pages, resolved menus) requires Pro.

Are ACF options pages included automatically?

No. You enable a single option to include all registered ACF options pages as top-level properties. When the option is off they are not added to the response. Use the Pro schema editor (per-property control or custom schema) to filter or restructure the output.

Can I restrict access to this endpoint?

Yes. Like any route, /wp/v2/settings can have auth enforcement, rate limiting, and HTTP method restrictions applied via the Routes panel.

Released under the GPL-2.0-or-later License.