RKX API Studio lets administrators create and manage custom read-only (GET) REST API endpoints visually from the WordPress admin, returning only the response data that a headless front end, mobile app, or external integration needs.<\/p>\n\n
X-RKX-API-Studio-Key<\/code>) for individual endpoints.<\/li>\n- JSON export and import of endpoint configurations and cache settings.<\/li>\n<\/ul>\n\n
All Free endpoints are served under the fixed REST namespace rkx-api-studio\/v1<\/code> (for example, \/wp-json\/rkx-api-studio\/v1\/your-endpoint<\/code>). RKX API Studio works standalone and does not require an external account or license key.<\/p>\n\nExtend RKX API Studio with Pro<\/h4>\n\n
RKX API Studio Pro is a separately distributed add-on that extends the Free plugin with advanced capabilities for custom REST API development, integrations, and authentication:<\/p>\n\n
\n- Custom REST API namespaces<\/li>\n
- Write endpoints (
POST<\/code>, PUT<\/code>, and DELETE<\/code> operations)<\/li>\n- Advanced Custom Fields (ACF) integration<\/li>\n
- Structured Gutenberg block parsing<\/li>\n
- Advanced multi-rule Regex formatters<\/li>\n
- Named API keys with per-endpoint access assignment<\/li>\n<\/ul>\n\n
Learn more on the RKX API Studio product page<\/a>.<\/p>\n\nSecurity and data handling<\/h3>\n\n\n- Only administrators (users with the manage_options capability) can create, change, import or delete endpoints and keys.<\/li>\n
- Only post types and taxonomies that WordPress marks as public and REST-visible can be used as data sources. Only published, non-password-protected posts are returned.<\/li>\n
- Protected custom fields (for example keys beginning with an underscore) are never exposed.<\/li>\n
- Protected endpoints require the
X-RKX-API-Studio-Key<\/code> request header. The API key is shown once when generated and is stored only as a keyed hash.<\/li>\n- Endpoint configurations, settings, the key hash and the response cache are stored in your WordPress database. Deactivation keeps this data. Uninstalling deletes it only if you enable \"Delete data on uninstall\" in the settings; on Multisite data is always kept.<\/li>\n
- Exports never contain API keys.<\/li>\n<\/ul>\n\n
External services<\/h3>\n\n
This plugin does not connect to any external service. It makes no remote requests for licensing, telemetry or updates, and loads no remote scripts, styles, fonts or images. Updates are provided through WordPress.org. Documentation and product information links in the admin interface open https:\/\/rkxbeta.com in your browser only when you click them.<\/p>\n\n
Source code<\/h3>\n\n
The plugin includes its unminified JavaScript, TypeScript and CSS sources and build instructions in the source\/ directory (see source\/BUILD.md). Third-party licenses and copyright notices are listed in THIRD-PARTY-NOTICES.txt.<\/p>\n\n
Documentation and support<\/h3>\n\n
Documentation<\/a> | Contact and support<\/a><\/p>\n\n\n\n- In your WordPress admin go to Plugins > Add New, search for \"RKX API Studio\", then install and activate it. Alternatively upload the plugin ZIP through Plugins > Add New > Upload Plugin.<\/li>\n
- Open RKX API Studio in the admin menu and create your first endpoint.<\/li>\n
- To protect endpoints, generate an API key under RKX API Studio > Settings > Security and enable \"Require API Key\" on the endpoint.<\/li>\n<\/ol>\n\n
Requirements: WordPress 6.8 or later and PHP 8.0 or later.<\/p>\n\n\n
\nWhich REST namespace do endpoints use?<\/h3><\/dt>\nEvery endpoint is available under rkx-api-studio\/v1<\/code>.<\/p><\/dd>\nIs data deleted during deactivation?<\/h3><\/dt>\nNo. Data is deleted only when you uninstall the plugin after enabling \"Delete data on uninstall\". If the RKX API Studio Pro add-on is still installed, or on Multisite, data is kept.<\/p><\/dd>\n
Can endpoints write data?<\/h3><\/dt>\nNo. RKX API Studio provides read-only GET endpoints.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.0<\/h4>\n\n
First public release.<\/p>","raw_excerpt":"Build clean, read-only REST API endpoints for your content visually.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/398899","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=398899"}],"author":[{"embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/rkxbeta"}],"wp:attachment":[{"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=398899"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=398899"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=398899"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=398899"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=398899"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ka.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=398899"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}