WP REST API Team Proposes to Merge Content Endpoints Into WordPress 4.7
Over the weekend, the WP REST API team published a proposal to merge the API endpoints for content types into WordPress 4.7. This is the second in a two-part proposal, which merged the infrastructure for the API into core in October 2015. Since that time the team has worked on polishing the content endpoints and making changes to core that are necessary to support the API. The endpoints proposed for merge include posts, comments, terms, users, meta, and settings management. This includes public access as well as authenticated access via the OAuth 1 protocol. The team selected OAuth 1 over the newer OAuth 2 protocol, because OAuth 2 requires HTTPS with a modern version of TLS. As WordPress core doesn’t require HTTPS, the team did not want to make it a requirement for using the API.
“This merge proposal represents a complete and functional Content API, providing the necessary endpoints for mobile apps and frontends, and lays the groundwork for future releases focused on providing a Management API interface for full site administration,” said Ryan McCue in the proposal posted on behalf of the WP REST API team.
Preliminary feedback in the comments so far has been supportive
Source: https://managewp.org/articles/13588/wp-rest-api-team-proposes-to-merge-content-endpoints-into-wordpress-4-7
source https://williechiu40.wordpress.com/2016/10/11/wp-rest-api-team-proposes-to-merge-content-endpoints-into-wordpress-4-7/