Atte Liimatainen

<p>WordPress plugin that helps to serve content through REST routes and gives<br />
customizability to developers through filters.</p>
<h3>Available Routes</h3>
<ul>
<li><code>/wp-json/arha/v1/post</code></li>
<li><code>/wp-json/arha/v1/page</code></li>
<li><code>/wp-json/arha/v1/options</code></li>
<li><code>/wp-json/arha/v1/archive</code></li>
</ul>
<h3>Example queries</h3>
<ul>
<li><code>/wp-json/arha/v1/post?post_type=POST_TYPE&slug=SLUG</code></li>
<li><code>/wp-json/arha/v1/page?path=PATH</code></li>
<li><code>/wp-json/arha/v1/options</code></li>
<li><code>/wp-json/arha/v1/archive?post_type=POST_TYPE&posts_per_page=POSTS_PER_PAGE&paged=PAGED&orderby=ORDERBY&order=ORDER</code></li>
</ul>
<h3>tax_query and meta_query in archive-route</h3>
<ul>
<li><code>tax_query</code> and <code>meta_query</code> are supported and they work how the query is built for it in <code>new WP_Query()</code></li>
<li>both needs their values to bes passed in as stringified json</li>
</ul>
<h3>Multiple post_types in archive-route</h3>
<ul>
<li>To pass multiple post_types in archive-route, use syntax that lets PHP read GET-param as an array. https://stackoverflow.com/a/9547490</li>
</ul>
<h3>Filters</h3>
<ul>
<li>
<p>To exclude querying specific post types from <code>post</code>– and <code>archive</code>-routes, you<br />
can use following filters:</p>
<p>`<br />
add_filter(‘arha_routes/archive_excluded_post_types’, ‘exclude_post_types’);<br />
add_filter(‘arha_routes/post_excluded_post_types’, ‘exclude_post_types’);</p>
</li>
</ul>
<p>function exclude_post_types($excluded_post_types) {<br />
  $excluded_post_types = [‘post’];<br />
  return $excluded_post_types;<br />
}<br />
    `</p>
<ul>
<li>To format <code>post</code>-route’s post before it’s served to client, use <code>arha_routes/format_post</code>-filter<br />
`<br />
add_filter(‘arha_routes/format_post’, ‘format_post’);</li>
</ul>
<p>function format_post($post) {<br />
  return $post;<br />
}<br />
    `</p>
<ul>
<li>To format <code>page</code>-route’s post before it’s served to client, use <code>arha_routes/format_page</code>-filter<br />
`<br />
add_filter(‘arha_routes/format_page’, ‘format_page’);</li>
</ul>
<p>function format_page($page) {<br />
  return $page;<br />
}<br />
    `</p>
<ul>
<li>
<p>To format <code>archive</code>-route’s posts before they are served to client, use <code>arha_routes/format_archive_post</code>-filter</p>
<p><code>add_filter('arha_routes/format_archive_post', 'format_archive_post');<br />
function format_archive_post($post) {<br />
return $post;<br />
}</code></p>
</li>
<li>
<p><code>options</code>-route returns empty result by default. To add content to it, use <code>arha_routes/format_options</code>-filter<br />
`<br />
add_filter(‘arha_routes/format_options’, ‘format_options’);</p>
</li>
</ul>
<p>function format_options($options) {<br />
  return $options;<br />
}<br />
    `</p>
<ul>
<li>
<p>By default Arha Routes returns only published content with post-, page- and archive-route, this can be modified by adding following filters.<br />
`<br />
// for archive route<br />
add_filter(‘arha_routes/allowed_post_statuses_archive’, ‘allowed_post_statuses’);<br />
// for post route<br />
add_filter(‘arha_routes/allowed_post_statuses_post’, ‘allowed_post_statuses’);<br />
// for page route<br />
add_filter(‘arha_routes/allowed_post_statuses_page’, ‘allowed_post_statuses’);<br />
function allowed_post_statuses($post_statuses) {<br />
// … change post_statuses array</p>
<p>return $post_statuses;<br />
}<br />
`<br />
After adding setting up these filters, request can include “post_status” parameter and it will be compared to $post_statuses array.</p>
</li>
</ul>
<h3>SearchWP</h3>
<p>Arha Routes supports SearchWP-plugin, which lets WP users to make keyword search engine for their content.</p>
<p>Activating SearchWP-plugin adds optional keyword-search functionality to <code>archive</code>-route. This is done by adding <code>s=KEYWORD</code> to the route<br />
– Example: <code>/wp-json/arha/v1/archive?post_type=products&posts_per_page=10&paged=1&orderby=date&order=ASC&s=monitor</code></p>
<h3>Polylang</h3>
<p>Arha Routes supports Polylang-plugin, which allows users to create content in multiple languages.</p>
<p>Activating Polylang changes how endpoints work:</p>
<ul>
<li>All routes require additional <code>lang</code>-param
<ul>
<li>Example: <code>/wp-json/arha/v1/archive?post_type=products&posts_per_page=10&paged=1&orderby=date&order=ASC&lang=en</code></li>
</ul>
</li>
<li><code>page</code>-route doesn’t support language prefix in path
<ul>
<li>Example: Permalink <code>/zh/info</code>, use like this <code>/wp-json/arha/v1/page?path=/info&lang=zh</code></li>
<li>Example: Permalink <code>/en/info/test</code>, use like this <code>/wp-json/arha/v1/page?path=/info/test&lang=zh</code></li>
</ul>
</li>
<li><code>options</code>-route passes <code>lang</code>-param forward to <code>arha_routes/format_options</code>-filter<br />
<code>add_filter('arha_routes/format_options', 'format_options', 10, 2);<br />
function format_options($options, $lang) {<br />
return $options;<br />
}</code></li>
</ul>
<h3>Polylang + SearchWP</h3>
<p>In order to make these two plugins work together, you need to add extra plugin to WP installation.</p>
<p>https://searchwp.com/extensions/polylang-integration/</p>


Arha Routes

Wordpress plugin that helps to serve content through REST routes and gives customizability to developers through filters.

meloniq

<p>GlotCore REST API extends GlotPress by exposing a REST API, allowing developers to integrate GlotPress with external systems, automate workflows, and build custom applications on top of the GlotPress translation platform.</p>
<h3>Experimental Notice</h3>
<p>This plugin is currently in an <strong>experimental stage</strong>.</p>
<p>API endpoints and features may change between releases.<br />
Version <code>0.1</code> is a foundational release intended for early adopters and developers.</p>
<p><strong>Versions between 0.1 and 1.0 do not guarantee backward compatibility.</strong></p>
<h3>Available Endpoints</h3>
<p>The plugin introduces REST API endpoints for interacting with GlotPress data:</p>
<ul>
<li><code>/gp/v0.1</code> – Base endpoint</li>
<li><code>/gp/v0.1/formats</code> – Retrieve available file formats</li>
<li><code>/gp/v0.1/glossaries</code> – Retrieve and create glossaries</li>
<li><code>/gp/v0.1/glossaries/{id}</code> – Retrieve, update, or delete a specific glossary</li>
<li><code>/gp/v0.1/glossaries/{id}/entries</code> – Retrieve and create glossary entries</li>
<li><code>/gp/v0.1/glossaries/{id}/entries/{entry_id}</code> – Retrieve, update, or delete a specific glossary entry</li>
<li><code>/gp/v0.1/languages</code> – Retrieve available languages</li>
<li><code>/gp/v0.1/originals</code> – Retrieve original strings</li>
<li><code>/gp/v0.1/originals/{id}</code> – Retrieve and delete a specific original string</li>
<li><code>/gp/v0.1/projects</code> – Retrieve and create projects</li>
<li><code>/gp/v0.1/projects/{id}</code> – Retrieve, update, or delete a specific project</li>
<li><code>/gp/v0.1/projects/{id}/permissions</code> – Retrieve and create project permissions</li>
<li><code>/gp/v0.1/projects/{id}/permissions/{permission_id}</code> – Retrieve and delete a specific permission</li>
<li><code>/gp/v0.1/profile/me</code> – Retrieve the authenticated user profile</li>
<li><code>/gp/v0.1/profile/{id}</code> – Retrieve a specific user profile</li>
<li><code>/gp/v0.1/translations</code> – Retrieve and create translations</li>
<li><code>/gp/v0.1/translations/{id}</code> – Retrieve, update, or delete a specific translation</li>
<li><code>/gp/v0.1/translation-sets</code> – Retrieve and create translation sets</li>
<li><code>/gp/v0.1/translation-sets/{id}</code> – Retrieve, update, or delete a specific translation set</li>
</ul>
<h3>Configuration</h3>
<p>After installation, GlotCore REST API is ready to use.</p>
<p>To explore the API, you may use tools like <strong>Postman</strong>.<br />
Postman collection and environment files are included with the plugin.</p>
<p>Please note that some endpoints require authentication.<br />
Suggested authentication method for testing is using <strong>Basic Authentication with WordPress Application Passwords</strong>.</p>


GlotCore REST API

Extends GlotPress with REST API endpoints for programmatic access to translation data.

Arha Routes vs GlotCore REST API