BackspaceX JSON Content Exporter
A lightweight WordPress plugin that exports posts, pages, custom post types, ACF fields, taxonomies, and media into Flutter-ready JSON files and provides a fast, secure REST API for mobile apps and headless projects.
Install
This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/thebackspacex/backspacex-json-content-exporter/archive/refs/heads/main.zipExport WordPress content, ACF fields, taxonomies, custom fields, and media as Flutter-ready JSON files and REST API responses.
Description
BackspaceX JSON Content Exporter provides a lightweight, read-only bridge between WordPress and mobile or external applications.
Key features:
- Dashboard JSON export for posts, pages, and custom post types.
- ACF fields, public custom fields, taxonomies, and featured images.
- Public or token-protected REST API with post-type controls.
- Pagination, search, sorting, date filters, and incremental sync.
- Deleted and trashed content tracking for offline synchronization.
- Configurable CORS, response cache, ETag, and Last-Modified headers.
- Rate limiting and optional privacy-safe request logging.
- Memory-safe streaming exports and resumable export sessions.
- Settings backup/import and diagnostics.
- Optional full data cleanup during uninstall.
Installation
- Upload the plugin ZIP from Plugins > Add New Plugin > Upload Plugin.
- Activate the plugin.
- Open BackspaceX Exporter > JSON Export or API Settings.
- Select the post types that may be exposed through the API.
- Enable token protection for non-public applications.
Frequently Asked Questions
Does the public API expose drafts or private posts?
No. REST API content endpoints only return published content. Dashboard exports remain restricted to administrators.
Are resumable export files public?
No. Version 1.0.0 serves completed session files through an authenticated, nonce-protected administrator download action and blocks direct web access where supported.
Does uninstall remove settings automatically?
No. Data is preserved by default. Enable the uninstall cleanup option in API Settings before uninstalling when complete removal is required.
Changelog
1.0.2
- Added an API setting to include or omit full post content in collection responses by default.
- Added per-request override support through include_content=true or include_content=false.
- Single content endpoints continue to include full content by default.
1.0.1
- Added lightweight collection responses: full post content is excluded by default from list endpoints.
- Added the
include_content=trueparameter to restore full content in collection responses. - Single-content endpoints continue to include full content by default.
- Prevented ACF values from being duplicated inside
custom_fieldswhen ACF output is enabled. - Decoded HTML entities in titles and other plain-text labels for cleaner mobile-app output.
1.0.0
- Stable production release.
- Secured resumable export downloads behind administrator authentication and nonces.
- Added direct-access protection files for the export directory.
- Added optional uninstall cleanup policy.
- Consolidated activation defaults for cache, rate limiting, logging, and cleanup.
- Completed release metadata, compatibility review, and package validation.
0.9.0
- Added configurable API rate limiting.
- Added privacy-safe request logging and diagnostics.
- Added settings export and import.
0.8.0
- Added resumable export sessions and progress tracking.
0.7.0
- Added memory-safe streaming and batch exports.
0.6.0
- Added response caching, ETag, Last-Modified, and HTTP 304 support.
0.5.0
- Added incremental sync and deleted-content tracking.
0.4.0
- Added shared formatting, token protection, post-type controls, and CORS settings.