<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>rest api on Publishing House</title>
    <link>https://publishinghouse.org/tags/rest-api/</link>
    <description>Recent content in rest api on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/rest-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The WordPress REST API: What Publishers Need to Know</title>
      <link>https://publishinghouse.org/the-wordpress-rest-api-what-publishers-need-to-know/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/the-wordpress-rest-api-what-publishers-need-to-know/</guid>
      <description>The WordPress REST API has been part of WordPress core since version 4.7. It transforms WordPress from a self-contained CMS into a content platform that can serve data to any application that can make an HTTP request — mobile apps, static front ends, third-party services, or another WordPress site. For publishers evaluating headless architecture or building integrations, understanding what the API provides (and how to use it) is increasingly essential.</description>
    </item>
    
  </channel>
</rss>
