Free Features · RKX API Studio 1.0.0
Export a backup
Open Settings → Tools and export endpoint configurations as JSON. Store the file securely and inspect it before sharing. Exporting configurations does not copy posts, terms, media files, ACF definitions, site activation or license authorization.
- Open Settings → Tools → Export.
- Choose the endpoint configurations you want to move.
- Download the JSON and keep it as a backup before making changes.
Import deliberately
On the destination, install the required edition and register the same content types, taxonomies and fields. Export its current configuration first, then choose the JSON import file. The importer validates configuration and offers duplicate-slug resolution. Review the result rather than assuming identical content or IDs across sites.
- Register the destination content types, taxonomies and fields first.
- Export the destination’s current configuration.
- Choose the JSON in Settings → Tools → Import.
- Review validation messages and resolve duplicate slugs deliberately.
- Test imported routes, term IDs and protection settings before giving clients the URLs.
Verify after migration
Check every saved URL, field, taxonomy term ID and protection setting. Recreate keys privately and activate Pro separately where needed. Unsupported Pro configurations remain stored but do not execute without authorization. Do not use import as a way to bypass a license or transfer secrets.