Pro Features · RKX API Studio 1.0.0
Custom namespaces
Licensed Pro adds Settings → API Namespaces. Create a valid namespace and select it in the endpoint builder. Request URLs then use /wp-json/ followed by that namespace and the endpoint slug. Existing clients must be updated when the URL changes.
Write actions require integration code
Pro supports authenticated POST, PUT and DELETE routes. These dispatch rkx_as_{method}_{slug} with the parsed payload; they do not automatically create, update or delete posts. A developer must implement validation and the action handler. Body size is limited to 1 MB. The default response reports success and the hook name, which alone does not prove your integration performed a write.
Validate before side effects
For a POST endpoint with slug webhook, use rkx_as_validate_post_webhook to reject invalid input, rkx_as_post_webhook to perform the operation, and rkx_as_response_post_webhook only to shape output. Test this on staging with synthetic data. Do not put the same write in both action and response filter; that would duplicate side effects.
Related guides
Public endpoints, API keys and access control