SleekView for REST API Toolbox: REST routes, log entries & rate-limits as tables
REST API Toolbox stores route settings in wp_options and request logs in its own log tables. SleekView turns route configuration and request history into sortable, filterable admin tables.
♾️ Lifetime License available
See REST traffic and route config in one working table
REST API Toolbox lets developers tune the WordPress REST API: disable specific routes, change response envelopes, add JWT or app-password authentication, and log inbound requests for debugging. Route settings live in wp_options under the plugin's option keys; request logs (when enabled) live in a dedicated wp_rat_logs-style table with method, route, response code, duration, and authenticated user.
SleekView reads both. A route configuration view shows every registered REST route with its current status (enabled, disabled, rate-limited), required authentication, and rate-limit setting. A request log view shows method, route, response code, duration, and user, with filters that combine status code and route prefix to find every /wp/v2/users request that returned 401 in the last hour.
Inline edits to route status and rate-limit settings route through the plugin's option update functions, so the changes apply on the next REST request the way a settings-screen save would. Log entries are read-only by design (logs should be immutable), but they can be sorted, filtered, and exported. The view coexists with the plugin's own settings screens, which remain available for the configuration UI itself.
Workflow
From split screens to one REST workbench
Pick the source
Compose columns
Save incident and audit views
Edit route settings inline
Sample columns
A typical REST request log view
wp_options + wp_rat_logs (REST API Toolbox request log table)
| Method | Route | Status | Duration | User | When |
|---|---|---|---|---|---|
| GET | /wp/v2/posts | 200 | 42 ms | anon | Just now |
| POST | /wp/v2/posts | 429 | 8 ms | alex@studio.co | 1 m |
| GET | /wp/v2/users/me | 401 | 12 ms | anon | 3 m |
| PATCH | /wp/v2/pages/12 | 200 | 118 ms | ria@design.io | 5 m |
Comparison
Default REST API Toolbox admin vs SleekView
Default Toolbox admin
- Route config and request logs live on different screens
- Filtering logs by status code plus route prefix isn't a saved view
- Bulk-changing route status across endpoints is screen-by-screen
- Rate-limit counters don't surface in the log alongside the route
- Per-role saved views for ops and developers aren't part of the UI
SleekView
- Route config and logs in adjacent saved views
- Filter by status code, method, and route prefix together
- Inline toggle route status and rate-limit settings
- Sort by duration to find slow endpoints in one click
- Save per-role views for incident response and routine audit
Features
What SleekView gives you for REST API Toolbox
Routes as a working table
Every registered REST route as a row with its enabled status, required auth, and rate-limit setting. Bulk-toggle route status without bouncing between the plugin's settings screens.
Stacked log filters
Filter the request log by method, status code, route prefix, and user in one saved view. "All 401s on /wp/v2/users in the last hour" becomes a single saved filter.
Inline route toggles
Disable a route or update its rate-limit setting inline. SleekView writes through the plugin's option update functions so the change applies on the next REST request without a manual settings save.
Audience
Who uses SleekView for REST API Toolbox
Incident responders
Open the log view filtered to non-2xx responses to triage a spike. Sort by duration to find slow endpoints, then disable a route inline if it's the source of the load.
API developers
Watch which routes integrations actually hit. Filter by user agent or app-password user to see how each integration uses the API, and adjust rate limits inline based on the data.
Platform operations
Audit REST traffic patterns over time. Filter to write methods on sensitive routes, save the view as a weekly review, and catch spikes before they become incidents.
The bigger picture
Why REST traffic and route config belong in one admin table
REST API Toolbox solves a real operational problem: the WordPress REST API is public by default, surface-rich, and not always easy to tune. The plugin lets you disable specific routes, add stricter authentication, and log inbound requests for debugging. The catch is that route configuration and request logs live on separate screens, and the relationship between them ("this route is being hammered, should we tighten its rate limit?") is the whole reason teams installed the plugin in the first place.
The data is there; the UI just doesn't put it in one place. SleekView treats both as what they are: tabular data that gets useful when you can sort, filter, and act on it together. Route config becomes a sortable table with status, auth, and rate-limit as columns.
Logs become a sortable table with method, route, status code, duration, and user. Inline route toggles route through the plugin's existing update path so changes apply on the next request. Incident response, capacity audits, and integration-debugging finally happen on one screen instead of three.
Questions
Common questions about SleekView for REST API Toolbox
Yes. REST API Toolbox writes request logs to its own log table when logging is enabled, and SleekView reads from there. Route configuration comes from the plugin's wp_options keys.
Yes. SleekView writes through the plugin's option update functions, the same path the settings screen uses. The change applies on the next REST request without requiring a separate save.
Yes. The log table includes the resolved user ID for authenticated requests, and SleekView joins to wp_users so the user's email shows in the row. Anonymous requests render with an anon placeholder.
Yes. SleekView paginates against the log table's primary key and only loads the columns you've added to the visible view. Filtering uses the table's existing indexes on route, status, and timestamp.
Yes. Export the visible rows as CSV with the applied filters and column set. Incident retros can grab a snapshot of the 5-minute window around an incident without writing SQL.
No. SleekView is admin-only and doesn't run on REST requests. The plugin's own log-write overhead is unchanged. SleekView's queries only run when an admin opens the view.
Yes. SleekView reads the live REST route registry via rest_get_server()->get_routes() when the route view loads, so any routes added or removed by activating a plugin appear or disappear immediately.
Logs stay in the plugin's log table. Route settings stay in wp_options. The plugin's own settings screens remain available, and nothing about the REST API or its logging changes.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Lemonsqueezy Wp
- Bigcommerce
- Woocommerce Min Max Quantities
- Wp Customer Reviews
- Wc Marketplace
- Woocommerce Pricing Deals
- Woocommerce Pre Order Pro
- Woocommerce Name Your Deal
- Woocommerce Ccavenue
- Woocommerce Paymongo
- Woocommerce Sendcloud
- Amazon Product Importer
- Woocommerce Easyship
- Funnelkit Funnel Builder
- Woocommerce Favorites