SleekView for WP Typed Routes: typed route, schema, and usage tables
WP Typed Routes registers strictly typed REST routes with schema, input validation, and capability checks. SleekView turns the registry, schema rows, and usage log into a sortable, filterable admin table.
♾️ Lifetime License available
See every typed REST route, its schema, and how often it's called
WP Typed Routes stores route definitions in a dedicated wptr_routes table with columns for namespace, route, method, capability, schema JSON, and active flag. Companion data lives in wp_options under the wptr_ prefix for global configuration. Usage metrics (when enabled) are recorded in a route log so each route knows how often it has been called and how long calls take on average.
SleekView reads wptr_routes directly and joins in the usage log to expose each route as a row. The namespace, method, required capability, schema field count, average response time, and call count all become first-class columns. Schema details (input fields, response fields, deprecated entries) expand inline so an audit of "every route that takes an unvalidated string" is a one-click filter.
Inline edits to the active flag, capability, and TTL route through WP Typed Routes' own update API so schema validation reruns and the registered route count stays in sync. Direct table writes are restricted to administrative scenarios and always emit an audit row. Schema fields themselves remain code-defined; SleekView is read-only on the schema rows by design.
Workflow
From wptr_routes to a real typed route table
Pick the source
wptr_routes table and the related wptr_route_log for usage data.
Compose columns
Save scoped views
Edit inline
Sample columns
A typical WP Typed Routes view
namespace, capability, schema fields, and recent calls as columns.
wptr_routes + wp_options (wptr_ prefix) + wptr_route_log
| Route | Method | Capability | Schema fields | Calls (24h) | Status |
|---|---|---|---|---|---|
| /typed/v1/leads | POST | edit_posts | 8 | 2,418 | Active |
| /typed/v1/checkout | POST | read | 14 | 8,902 | Active |
| /typed/v1/admin/users | GET | manage_options | 6 | 12 | Paused |
| /typed/v0/legacy | POST | read | 3 | 1 | Deprecated |
Comparison
Default WP Typed Routes admin vs SleekView
Default WP Typed Routes admin
- Route list paginates without sort on capability or schema size
- Schema details are buried per route, not surfaced as a list
- No usage metrics next to the route definitions
- Deprecated routes are flagged but not listed together
- Bulk activation or capability changes are not supported in the stock UI
SleekView
-
Every
wptr_routescolumn becomes a sortable, filterable field -
Join usage from
wptr_route_logas calls and average duration - Filter to deprecated or paused routes in one click
-
Inline toggle
activeand bulk reassign capability - Saved views split engineering from compliance audits
Features
What SleekView gives you for WP Typed Routes
Typed routes as a real table
wptr_routes stores everything: namespace, method, capability, schema, active flag. SleekView pivots it into rows you can actually search.
Usage joins from wptr_route_log
Calls per day, average response time, and last seen timestamp join in. The popular typed route and the deprecated one surface in the same sort.
Audit capability mismatches
Filter to every POST route guarded only by read. The audit ticket writes itself and the fix happens inline through the plugin's update API.
Audience
Who uses SleekView for WP Typed Routes
Platform engineers
Audit typed routes by namespace, method, and schema size. Find legacy v0 entries that should retire before the next release.
Security reviewers
Filter to routes with weak capability checks or large schemas. Annotate findings inline and archive once the route is fixed.
Integration teams
Confirm which typed routes a partner integration depends on before scheduling a deprecation. The usage column tells you exactly how loud the change will be.
The bigger picture
Why typed REST surfaces need an audit table
Typed REST routes are the maturity step every WordPress API surface eventually reaches. WP Typed Routes adds the discipline: validated input, declared output, documented capabilities, and a real table to back it all up. The cost of that discipline is that a serious site ends up with hundreds of typed routes, and the default admin presents them as a paginated list that does not sort on the things that actually matter.
Schema size, capability, deprecation status, and usage all become invisible at scale. SleekView treats wptr_routes the way it deserves to be treated: as a real table with usage data joined in. Platform engineers find the legacy v0 entries.
Security reviewers find the routes with weak guards. Integration teams confirm what a deprecation will break before they ship it. The discipline of typed routes pays off when the operations layer can keep up.
SleekView is that layer.
Questions
Common questions about SleekView for WP Typed Routes
No. Schema fields are code-defined, and SleekView is read-only on schema rows. Inline edits are limited to operational fields like active flag, capability, and TTL, all of which route through the plugin's own update API.
Yes. SleekView calls the plugin's update functions, which revalidate the route definition against the current schema. Invalid edits roll back without affecting the live registry.
Yes. The route view works without logging. The usage columns appear blank or hidden when wptr_route_log is not in use, and the rest of the table behaves normally.
Yes. Any route registered through the plugin's own registration API, whether stored in wptr_routes or added at runtime through filters, appears in the table. Runtime-only routes are flagged as such so engineers know which ones lack a persisted definition.
Deprecated routes carry a flag in wptr_routes that SleekView exposes as a column and a one-click filter. A deprecation audit is a saved view rather than a grep through code.
Yes. SleekView paginates against the primary key on wptr_routes and uses indexed filters on namespace, method, and active flag. Usage joins lazy-load so initial table queries stay lean.
Bulk changes batch through the plugin's update API and any group that fails validation rolls back without affecting the others. SleekView records the batch result for audit purposes.
Yes. Per-role views can grant read-only access to the route table without the capability to toggle active flags or change capabilities. SleekView honors WordPress capability checks on every column.
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
- Woocommerce Color Swatches
- Ecwid
- Aelia Tax Display By Country
- Woocommerce Quotes Orders
- Wcam Marketplace
- Woocommerce Bulk Stock Management
- Woocommerce Product Addons Pro
- Woocommerce Product Variations Swatches
- Shipperhq Woocommerce
- Paystack Woocommerce
- Edd Amazon S3
- Woocommerce Blocks
- Yith Woocommerce Anti Fraud
- Wcfm Delivery
- Wcfm Bookings