With the latest versions, the WordPress API has matured into a secure and flexible solution that easily extends to cater to complex features. This was considered to be an insecure feature that exposed the security vulnerabilities of WordPress, hence, was disabled by default in earlier versions. As of Version 3.5, XML-RPC is enabled by default and the enable/disable option from the admin dashboard has been completely removed. As developers, now we don't have to worry about the security risks identified in earlier releases.
The existing APIs mainly focus on addressing functionalities for blogging- and CMS-related tasks. In web applications, we can make use of these API functions to build an API for third-party applications and users. The following list contains the existing components of the WordPress API:
Posts
Taxonomies
Media
Comments
Options
Users
The complete list of components and respective API functions can be found in the WordPress codex at http...