[wp-meta] [Making WordPress.org] #8124: Plugin Info API need to provide schema of fields for downstreams
Making WordPress.org
noreply at wordpress.org
Tue Nov 4 22:49:12 UTC 2025
#8124: Plugin Info API need to provide schema of fields for downstreams
--------------------------+---------------------
Reporter: yookoala | Owner: (none)
Type: defect (bug) | Status: new
Priority: low | Milestone:
Component: API | Resolution:
Keywords: |
--------------------------+---------------------
Changes (by dd32):
* priority: normal => low
Comment:
Officially, the WordPress.org API's are for consumption by WordPress
itself only, and 3rd-party clients are supported in a best-effort manner.
What benefit would a schema provide to them? Other than documenting the
properties contents? As the output of the API may change (in a backwards-
compatible manner) at any time with an update to the schema.
> Most notably a "url" field was in the API, but is seemingly no longer
exists.
A 'url' field has never been present as far as I know.
I suspect this is a copy-paste error in the documentation from another
API.
The underlying data endpoint for the plugin endpoint is here:
https://github.com/WordPress/wordpress.org/blob/trunk/wordpress.org/public_html
/wp-content/plugins/plugin-directory/api/routes/class-plugin.php
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/8124#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list