# airesvsg/acf-to-rest-api

Exposes Advanced Custom Fields Endpoints in the WordPress REST API

Repository: https://github.com/airesvsg/acf-to-rest-api
Canonical: https://ross.abutalabs.com/products/acf-to-rest-api
Homepage: https://wordpress.org/plugins/acf-to-rest-api/
Language: PHP
License Family: other
Topics: wordpress, rest, api, acf, custom, fields, rest-api, wp-api, wp, wordpress-plugin
Last push: 2024-12-31T16:15:54+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 3896, "days_push": 610, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1362, forks 120 (observed 2026-08-28T04:04:30.296132+00:00)

## What it is
A WordPress plugin that exposes Advanced Custom Fields (ACF) data through dedicated endpoints in the WordPress REST API. It adds /wp-json/acf/v3 routes for posts, pages, users, taxonomies, comments, media, custom post types, and options pages, with read and edit permissions and developer filters.

## Use cases
- expose acf custom fields in the wordpress rest api
- build a headless wordpress site with custom fields
- fetch acf fields for a post via json endpoint
- update acf field values through the rest api
- get acf options page values over rest
- use wordpress as a cms backend for a javascript frontend

## When to choose
- you run a legacy WordPress site with ACF and need custom fields in REST responses
- you're building a headless WordPress frontend that reads ACF data
- you need per-field REST endpoints with customizable permissions via filters

## When to avoid
- starting a new project - the plugin was closed on WordPress.org in January 2026 due to a security issue
- you use ACF 5.9+ which has native REST API field support built in
- you need actively maintained, security-audited software

## Facets
- artifact type: plugin
- maturity: abandoned
- function: api-framework, http-server, middleware
- domain: cms, web-development, apis, backend
- platform: php, self-hosted
- tags: wordpress-plugin, acf, rest-api, headless-wordpress, custom-fields, security-issue, web-server

## Member repositories
- airesvsg/acf-to-rest-api (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:30.296132+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:41:29.054809+00:00, confidence not recorded.
  - readme: https://github.com/airesvsg/acf-to-rest-api (fetched 2026-08-28T04:04:30.296132+00:00, sha 0e30a55df196)
  - homepage: https://wordpress.org/plugins/acf-to-rest-api/ (fetched 2026-08-29T11:59:12.293574+00:00, sha 7a4834ad2ddd)
  - site_page: https://wordpress.org/documentation (fetched 2026-08-29T11:59:12.321678+00:00, sha bd7786ab20ae)
  - site_page: https://wordpress.org/about (fetched 2026-08-29T11:59:12.335930+00:00, sha 7beb23faf433)
  - site_page: https://wordpress.org/about/privacy (fetched 2026-08-29T11:59:12.353698+00:00, sha ae4fa61fc31e)
- Data as of 2026-08-30T08:39:29.467469+00:00.