Blockrush API Request Diagnostics
Analyze outbound third-party calls made through the WordPress HTTP API.
Use with caution
Blockrush API Request Diagnosti… works, but test it on a staging site before relying on it in 2026. Was last updated 2 months ago, and scores 55/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Blockrush API Request Diagn… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| api | >100 |
| diagnostics | >100 |
| http | >100 |
| monitoring | >100 |
| woocommerce | >100 |
About Blockrush API Request Diagnostics
From the official readme · v1.4.8Description
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.
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.
Frequently asked questions
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.
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.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Blockrush API Request Diagnos… alternatives
All api plugins →
FAQ
Blockrush API Request Diagnostics: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 2, 2026
Is Blockrush API Request Diagnosti… free?
Yes. Blockrush API Request Diagnosti… is free to download and use from the official WordPress.org plugin directory.
Is Blockrush API Request Diagnosti… safe to use in 2026?
Blockrush API Request Diagnosti… works, but test it on a staging site before relying on it in 2026. Was last updated 2 months ago, and scores 55/100 on our health check.
How many websites use Blockrush API Request Diagnosti…?
Blockrush API Request Diagnosti… is active on <10 WordPress websites and has been downloaded 153 times since it launched in August 2026. It was downloaded 66 times in the last 30 days.
Does Blockrush API Request Diagnosti… work with WordPress 7.1?
Blockrush API Request Diagnosti… is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Blockrush API Request Diagnosti… need?
Blockrush API Request Diagnosti… requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Blockrush API Request Diagnosti… last updated?
The latest version, 1.4.8, was released on August 17, 2026 (2 months ago).
Who makes Blockrush API Request Diagnosti…?
Blockrush API Request Diagnosti… is developed and maintained by blockrush.
What are the best alternatives to Blockrush API Request Diagnosti…?
The most popular alternatives to Blockrush API Request Diagnosti… are WP Consent API (200K+ installs), Disable REST API (80K+ installs) and Mailgun for WordPress (80K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
