WordPress plugin intelligence profile

API Request Collector

This plugin is made for plugin developers that work with APIs and need easy access to debug information.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 3.6
Current version0.1
WordPress coverageTested up to WordPress 3.6
Minimum stackWP 3.5.1 · PHP —
Directory statusactive
Last directory update30 Apr 201313y ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records API Request Collector version 0.1 as active, updated 13y ago and tested up to WordPress 3.6.

Overview

About this plugin

This is a very simple plugin that creates a new adminbar menu with a list of pertinent API calls used on a page.

However, no good thing happens in a vacuum, and you good folks, are developers.

In order to log API calls, you should invoke the log_api_call() method of the $ab_api_logger global object. Of course, if you prefer, you can instantiate your own object using the AB_API_Logger class.

The log_api_call() method takes two properties. The first is an array of URLs that will be included as menu items (easy access, easy click to see responses). By default, the plugin maintains a property $api_calls with this array and uses it to parse out the menu items.

However, if you wish to maintain your own array, you can do that too. The plugin takes care of what it needs, and you can feel free to maintain what you need.

The second argument for the log_api_calls() method is the URL that will be added to the adminbar menu. You can escape it if you want, but I will as well for security.

The reason I built this plugin is because I deal with APIs a lot. My normal approach to API integration is to use a pre-existing PHP library or, more commonly, build a library around the API so I can use it easily without having to remember everything.

Usually, this means I create a class and that class is filled with methods that construct a URL based on parameters and then use wp_remote_get() to retrieve the response from the API. Anytime after the URL is created, invoke this plugin:

apikey=asdfASD234&post_id=213) global $ab_api_logger; $ab_api_logger->log_api_call( $ab_api_logger->api_calls, $api_url ); }

Pull requests can be submitted via Github

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • api
  • development
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 3.6

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 3.6.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to3.6
Minimum requirementsWordPress 3.5.1 · PHP not listed
Update activity30 Apr 201313y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.