[wp-meta] [Making WordPress.org] #6061: Download stats API returning unexpected results

Making WordPress.org noreply at wordpress.org
Tue Feb 1 01:18:51 UTC 2022

#6061: Download stats API returning unexpected results
 Reporter:  pyves   |       Owner:  (none)
     Type:  defect  |      Status:  reopened
 Priority:  normal  |   Milestone:
Component:  API     |  Resolution:
 Keywords:          |

Comment (by dd32):

 The codex (https://codex.wordpress.org/WordPress.org_API) is a public
 wiki, anyone can add documentation there if they wish, it's not 'official
 documentation', although I've edited incorrect data out of it before. The
 Codex is deprecated and pending shutdown, that page hasn't been migrated
 to any "officially maintained" locations for a reason.

 The plugin-info endpoint (https://api.wordpress.org/plugins/info/1.0) is
 versioned as the input/output format has changed over time, and is used by
 a large number of clients, it's anticipated that it will remain used and
 so there's no issues relying upon it, it's versioned because the WordPress
 software uses those endpoints and older verisons of WordPress still use
 the older versions of those APIs. It's not intended to be used outside of
 WordPress.org/WordPress but we don't prevent it. You could make a request
 against it to verify if a slug is valid first.

 The stats endpoints are not designed for "public consumption", rather for
 WordPress.org-only uses. We don't prevent others from accessing the
 endpoints, but we don't support it. As noted it returns invalid data for
 invalid input due to design, due to abuse of the API. There's versioning
 included, but mostly to keep it inline with other API's on w.org, it'll
 change if the graphs that use it need to change (which has happened
 numerous times in the past).

Ticket URL: <https://meta.trac.wordpress.org/ticket/6061#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list