Skip to content

Nexter Fields and the WordPress REST API

Updated On : November 12, 2026By : Reading Time : 2 minutes

Key Takeaways

  • Nexter registra los valores de campo como post meta, y los tipos simples se exponen en REST mientras que los estructurados no se exponen porque no son un escalar plano.
  • Repeater y Relationship requieren Nexter Pro Extensions 4.8.0 o posterior; en Nexter Extension solo, no se pueden añadir y un campo existente queda bloqueado, con el valor de solo lectura y sin borrarse al guardar.
  • La lectura por REST usa /wp-json/wp/v2// y el valor aparece en el objeto meta con la clave _nxt_gf__; para campos no públicos se necesita una solicitud autenticada.
Table of Contents

Field values can be read through the WordPress REST API, which is how the block editor and any headless front end reach them.

Repeater and Relationship require Nexter Pro Extensions 4.8.0 or later. On Nexter Extension alone neither type can be added, and an existing field of either type is locked: the value is kept read-only and is never cleared on save.

What It Does

Nexter registers field values as post meta. Simple types are exposed in REST; structured ones are deliberately not, because their shape is not a flat scalar.

Before You Start

  • A field group whose location rules match the post type you are querying.
  • A post with values saved.
  • For anything non-public, an authenticated request.

Read a Field Value over REST

  1. Request the post as usual — /wp-json/wp/v2/<post-type>/<id>.
  1. Look in the meta object of the response.
The Presentation tab, where per-field display settings live
  1. Field values use the meta key pattern _nxt_gf_<group>_<field>.
  1. If a field you expect is absent, check whether its type is exposed — see the limitations.

Limitations

  • Repeater, relationship and link values are not exposed by default. Their stored shape is an array or a structure, not a flat scalar, so they are registered with REST exposure off. Read them in PHP, or add your own REST field.
  • Registered meta carries no object_subtype, so a registered field key applies across post types rather than being scoped to one.
  • The Content Fields admin API — the routes that create and edit field groups — is a separate, administrator-only surface. It is not for front-end use.

Troubleshooting

My repeater is missing from the REST response

That is by design. Structured values are not exposed by default. Read them server-side, or register your own REST field that returns the shape you want.

The meta object is empty

The post has no saved values, or the field group’s location rules do not match this post type.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Raise a ticket Now

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Join Us

Related Frequently Asked Questions

Why is my Nexter field missing from the WordPress REST API response?

Nexter registers field values as post meta, but only simple types are exposed in REST. Repeater, relationship, and link values are intentionally left out because their stored shape is not a flat scalar. If a field is missing, the first thing to check is whether its type is one of those structured values, since that changes how it can be read and whether it appears in the response at all.

How do I read a Nexter field value through the REST API?

The post endpoint is the starting point: /wp-json/wp/v2//. The value appears in the response’s meta object, and Nexter uses the meta key pattern _nxt_gf__. That matters because the field name alone is not enough to find it. If the key is absent, the next question is whether the field type is exposed in REST.

Can I use Nexter fields with a headless WordPress front end?

Nexter fields can be read through the WordPress REST API, which is the same path used by the block editor and any headless front end. That makes simple field values usable outside normal theme rendering. The catch is that only simple types are exposed by default, so structured fields need server-side handling or a custom REST field if your front end depends on them.

What are the REST API limits for repeater and relationship fields in Nexter?

Repeater, relationship, and link values are not exposed by default because their stored data is structured rather than a flat scalar. Nexter keeps them out of REST exposure for that reason. If you need those values in an API response, read them in PHP or register your own REST field that returns the shape you want instead of expecting the default meta object to include them.

Why does my meta object come back empty in Nexter REST responses?

An empty meta object usually means one of two things: the post has no saved values, or the field group’s location rules do not match that post type. That distinction matters because an empty response does not always mean the field failed to save. In practice, matching the group location to the queried post type is just as important as saving data on the post itself.

Do I need Nexter Pro Extensions for repeater and relationship fields?

Repeater and Relationship require Nexter Pro Extensions 4.8.0 or later. On Nexter Extension alone, neither type can be added, and an existing field of either type stays locked: its value remains read-only and is never cleared on save. That means these field types are treated differently from simple fields from creation all the way through REST exposure.

Last reviewed: November 12, 2026

Related Docs

Add a Custom Field to a Post in WordPress
icon
Add a Custom Migration Source with nxt/import_sources
icon
Add Custom Fields to Taxonomy Terms in WordPress
icon
Add Custom Fields to User Profiles in WordPress
icon
Check Whether a Custom Field Exists or Has a Value
icon
Checkbox Field in WordPress
icon
123……………14