Get Custom Field - Plugixa FAQ for WordPress

Get Custom Field - Plugixa FAQ

GET /plugixa-faq/v1/custom-fields/{id}

Read one custom field definition.

Any signed-in user with the plugixa_faq_manage capability or WordPress’s edit_posts (Contributors and up, by default). Needs Plugixa FAQ Pro: the free build does not register this route, so it answers 404 there.

Request

GET https://your-site.example/wp-json/plugixa-faq/v1/custom-fields/5

Path parameters

Name	Type	Description
`id`	`integer`	The field’s id

Responses

`200` OK. `data` is the field.

{
  "success": true,
  "message": "",
  "data": {
    "id": "5",
    "field_key": "warranty",
    "field_label": "Warranty",
    "field_type": "text",
    "field_options": null,
    "placeholder": "e.g. 2 years",
    "is_required": false,
    "show_in_frontend": true,
    "menu_order": "1",
    "created_at": "2026-11-12 09:30:00",
    "created_by": null,
    "modified_at": "2026-11-12 09:30:00",
    "modified_by": null,
    "language_code": null,
    "translation_group": null
  }
}

Field	Type	Meaning
`data.field_options`	`array\|null`	Choices of a `select` field
`data.is_required`	`boolean`	Real boolean
`data.show_in_frontend`	`boolean`	Real boolean
`data.translations`	`array`	Only with WPML or Polylang active

Errors

Status	Code	When
`404`	`rest_error`	No field with that id.

Plus the errors every endpoint can return.

Examples

curl -s "https://your-site.example/wp-json/plugixa-faq/v1/custom-fields/5" \
  -u "admin:$WP_APP_PASSWORD"

<?php
$ch = curl_init('https://your-site.example/wp-json/plugixa-faq/v1/custom-fields/5');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_USERPWD        => 'admin:' . getenv('WP_APP_PASSWORD'),
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

const response = await fetch('https://your-site.example/wp-json/plugixa-faq/v1/custom-fields/5', {
  headers: {
    'Authorization': 'Basic ' + btoa(`admin:${process.env.WP_APP_PASSWORD}`),
  },
});
const { data } = await response.json();