Twitter0 Facebook0 Google+0 For starters, it was super tough trying to figure out how to give this post a title. I’ve settled on “A Creative Approach to Efficient and Scalable WordPress API Endpoints” because it seemed to do the topic the most justice. As WordPress continues to evolve into an application platform, it is being used more and more frequently as the backend to power APIs (REST and (un?)REST alike). You can clearly see this by all the initiative and excitement around the new JSON API that will make it into WordPress at some point in the future. I am excited about where this is headed because it means WordPress can easily be used to power web applications with consumable APIs, but since I am always concerned about performance, this post has come to life. The Problem The way to approaching the API and creating endpoints around it is somewhat puzzling. With the current architecture of WordPress, the majority of API endpoints hook into either the init or wp_loaded hooks because these are the first available actions where the WordPress backbone has been loaded. This is all well and good for ease of use, but from an API and architecture standpoint, this is almost lunacy. Let me
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.