Log HTTP Requests
View on WordPress.orgScores higher than 19% of indexed plugins
About
Log and view all WP HTTP requests
Security History
What It Does
Log HTTP Requests records every outgoing HTTP request that WordPress makes through its built-in WP_Http class, including calls to plugin update servers, external APIs, and third-party services. All requests are stored in a custom database table where you can browse, search, and inspect them directly from the admin dashboard. It is essentially a network sniffer scoped specifically to WordPress's own outbound HTTP traffic.
Who It's For
This plugin is well suited to developers and site builders who need to diagnose why a specific API call, update check, or webhook is failing on a production site. Agencies managing client sites, hosting support technicians, and anyone troubleshooting payment gateway or email deliverability issues will find the request log invaluable for narrowing down where a request is breaking.
Who Should Skip It
Casual site owners and non-technical users will get little value from this tool, and sites with heavy outgoing API traffic may find the database table growing quickly. If you only need to debug email specifically, a dedicated mail logging plugin will be more focused and easier to use.
The Bottom Line
Log HTTP Requests does one specific job and does it well, with a perfect user rating, active maintenance, and current WordPress compatibility. The small install base and complete absence of support tickets make it a harder choice for those who value community track records. For developers who need to see every outbound request WordPress makes, it is a focused utility worth installing.
Related Plugins
Pick this if your debugging focus is SMTP and email delivery rather than the full spectrum of outbound HTTP traffic.
Choose this for a lightweight, mail-only logging tool when HTTP request capture is unnecessary.
Reach for this when you want to shut down inbound REST access rather than monitor outbound HTTP calls.
Use this if you specifically need to send transactional email via Mailgun and log those sends.
Choose this when you actively want to build external API integrations rather than simply log existing ones.