Description
Blockrush API Request Diagnostics gives administrators and WooCommerce store managers a fast, private
view of outbound requests made through the WordPress HTTP API.
Highlights
- Groups calls by third-party destination.
- Expands destination groups into their individual recent calls.
- Tracks request volume, success rate, response time, transfer size, and source.
- Filters all calls by success, error, time, HTTP status, destination, URL, and source.
- Organizes calls chronologically with last-5-minute, last-hour, today, this-week, date-range, and exact custom periods.
- Opens a detailed request/response inspector.
- Produces a copyable, credential-safe cURL command for support and diagnostics.
- Fully suppresses recognized credentials before storage so Free never retains usable secrets.
- Adjustable local log retention and body-size limits, with conservative defaults of one day and 64 KB.
- Responsive, keyboard-accessible UI with no external JavaScript dependencies.
Capture scope
Blockrush API Request Diagnostics observes requests made through WordPress HTTP API functions such as
wp_remote_get() and wp_remote_post(). This includes WordPress core and most
well-behaved plugins, including WooCommerce extensions.
Calls made directly through raw cURL, sockets, or third-party SDK transports that
bypass the WordPress HTTP API cannot be observed from a WordPress plugin without
unsafe system-level interception.
Privacy and security
Recognized API keys, tokens, passwords, authorization headers, client secrets,
consumer credentials, signatures, and URL credentials are fully suppressed
before a log is inserted. Blockrush API Request Diagnostics does not
retain an unmasked copy.
Request bodies are captured by default with a 64 KB maximum. Authorized users
can adjust that limit in Settings. Response bodies are disabled by default.
Headers, status, duration, and byte size remain available when response bodies
are disabled.
Only administrators and WooCommerce users with manage_woocommerce can access
the dashboard, settings, and call details. All actions use WordPress nonces.
Filtered CSV and JSON exports are available through API Analyzer Pro.
Blockrush API Request Diagnostics stores logs only in the site’s own WordPress database. The plugin
does not send logs, telemetry, or personal information to Blockrush or any
other external service.
Because request bodies can contain customer or visitor information chosen by
other plugins, site owners should review their privacy obligations and retention
settings before enabling capture on a production site. Blockrush API Request Diagnostics provides
suggested text in WordPress’s Privacy Policy Guide.
External services
Blockrush API Request Diagnostics does not contact an external service on its own. It does not send
data to Blockrush, load remote assets, collect telemetry, or operate a
hosted component.
The plugin observes outbound WordPress HTTP API calls initiated by WordPress
core, themes, and other plugins. The destinations and information sent in those
calls are controlled by the software that initiated them, not by Blockrush API Request Diagnostics.
Site owners should review the terms and privacy policies of those services
separately.
Screenshots
Installation
- Upload the
blockrush-api-request-diagnosticsfolder to/wp-content/plugins/, or install its ZIP. - Activate Blockrush API Request Diagnostics in WordPress.
- Open API Analyzer in the WordPress admin menu.
- Generate normal store traffic, or use an integration’s test-connection action.
FAQ
-
Can the copied cURL command be run as-is?
-
No. Credentials are deliberately suppressed. Replace suppressed values with
valid secrets in a secure local environment before replaying the request. -
Does pausing capture affect existing logs?
-
No. It stops new capture only. Existing logs remain until their retention period
expires, an authorized user clears them, or the plugin is deleted. -
What happens on uninstall?
-
Deleting the plugin through WordPress removes its custom table, settings, and
scheduled cleanup event. Deactivation alone retains data. -
Does Blockrush API Request Diagnostics contact Blockrush?
-
No. Blockrush API Request Diagnostics has no hosted service, telemetry, tracking pixel, remote assets,
or update service outside WordPress.org. It observes calls initiated by WordPress
and other installed plugins and stores the resulting diagnostic logs locally.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Blockrush API Request Diagnostics” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Blockrush API Request Diagnostics” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.4.8
- Adopt a unique Blockrush-specific prefix for PHP classes, constants, functions, options, database tables, cron events, hooks, AJAX actions, and JavaScript globals.
1.4.7
- Add an accessible Refresh stats control with progress feedback and an updated-at confirmation.
1.4.6
- Make log retention and maximum body size adjustable in Free, with defaults of one day and 64 KB.
- Remove retention and body-size limits from Pro-only positioning.
1.4.5
- Rename the public plugin and requested WordPress.org slug to Blockrush API Request Diagnostics.
- Keep the established API Analyzer dashboard menu label for existing administrators.
1.4.4
- Move the export handler, CSV/JSON streaming, and export database queries entirely into the separate Pro add-on.
- Keep Free credential masking permanently fully suppressive; first/last-three previews now exist only in Pro.
- Move ignored-destination processing out of the Free package.
- Replace filter-gated paid implementations with complete Pro-owned services and neutral integration contracts.
1.4.3
- Set conservative initial defaults of one-day log retention and a 64 KB capture-body limit.
- Reserve ignored destinations for licensed Pro users.
- Enforce edition limits in capture, cleanup, and settings requests—not only in the interface.
- Harden nested XML and multipart credential suppression before storage.
- Move exports into a dedicated Export tab beside Destinations.
1.4.2
- Bound recursive, oversized, and unterminated HTTP payload analysis before storage.
- Reapply credential redaction after extension filters and cap unmatched request markers in persistent workers.
1.4.1
- Update public publisher branding to Blockrush.
1.4.0
- Fully suppress recognized credential values in Free before database storage.
- Move identifiable first/last-three credential previews to API Analyzer Pro.
- Move filtered CSV and JSON exports behind an active API Analyzer Pro license.
- Expand the Upgrade to Pro panel with accurate credential-preview and export benefits.
1.3.0
- Add an Upgrade to Pro tab with a focused feature comparison and an explicit Blockrush purchase link.
- Add extension points for the separately installed API Analyzer Pro license.
- Remove protected-destination Redact/Hide logic and rendering from Free; provide it only through the separately installed Pro add-on.
- Keep credential safety and all core diagnostics available without a license.
1.2.0
- Add neutral extension hooks for separately packaged add-ons.
- Limit the complete free edition to 7 or 14-day log retention.
- Move advanced Speed Insights to the separately distributed API Analyzer Pro add-on.
- Keep credential safety and core capture, analytics, and filtering free.
1.1.1
- Add an accessible header switch for instantly starting or pausing capture, with capture enabled by default.
1.0.1
- Harden credential redaction for cookies, proxy authorization, XML/SOAP, multipart forms, error messages, and additional token/session field names.
- Bound stored headers and enforce payload limits at capture and database boundaries.
- Add action-specific nonces, CSV formula-injection protection, download hardening, and multisite uninstall cleanup.
1.0.0
- Initial release with grouped calls, call-status filters, chronological time analysis, and speed insights.