WPML JSON API icon
Possibly abandoned Tested up to 3.4.2

WPML JSON API

This plugin filters the response content of requests made to the WordPress JSON-API to include data for translations created through the WPML Multilingual CMS plugin. One may also request the translation of response…

Active installs10+10+ tier
Downloads · 30d156▼ -4.9% vs prev. 30d
Rating—0 reviews
Health score23/100At risk
All-time downloads6.4KSince Sep 2011
Support resolved—No recent threads
RequiresWP 2.8PHP any
Downloads · 7d36▼ -12.2% week over week
Our verdict

Consider an alternative

WPML JSON API shows warning signs in 2026 — compare the alternatives below before installing. It runs on 10+ sites and was last updated 14 years ago, and scores 23/100 on our health check.

  • Small user base (10+ active installs)
  • Very few reviews so far
  • No update in 13 years
  • Only tested up to WordPress 3.4 (latest is 7.1)

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

257Aug 18Oct 1Nov 15
Yesterday6
Daily average (1y)4
Peak day10Jul 23, 2026
Last 12 months1.5K

Download spikes usually follow a new release — each site that auto-updates counts as a download.

Rankings

Where WPML JSON API stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
api >100 10,000 Best api plugins →
cms >100 973 Best cms plugins →
i18n >100 2,199 Best i18n plugins →
JSON >100 8,160 Best JSON plugins →
wpml >100 3,000 Best wpml plugins →

Version adoption

Share of active sites per release.

  • 0.1100.0%

About WPML JSON API

From the official readme · v0.1.3

Description

This plugin filters the response content of requests made to the WordPress JSON-API to include data for translations created through the WPML Multilingual CMS plugin. One may also request the translation of response objects to a supported target language.

The Office of Letters and Light uses this plugin to integrate WordPress and WPML with its Rails-built National Novel Writing Month event-site application. We use WordPress to manage all back-end site content and our Kiosk Ruby gem for consuming, caching, searching, and serving the content through Rails. This could not have been so easily accomplished without the well-built and extensible JSON-API for which we are grateful. And without the WPML plugin, we would not have such an intuitive and capable CMS i18n interface.

Usage

Please be familiar with the
JSON-API.

  1. Augmented response objects
    • 1.1. Language
    • 1.2. Translations
  2. Filtering response objects by language
    • 2.1. Specifying the language
    • 2.2. Filtered results
  3. Response object translation
    • 3.1 Specifying the target language
    • 3.2 Translated results
    • 3.3 Translatable objects and properties

1. Augmented response objects

1.1. Language

After enabling the WPML JSON-API plugin, response objects will contain the
language in which the object content was written.

Let’s take a look at an example response to a request made to http://wordpress.site.example/api/get_page/?dev=1&id=127.

{
  "status": "ok",
  "page": {
    "id": 127,
    "type": "page",
    "slug": "the-best-page",
    "url": "http:\/\/wordpress.site.example\/the-best-page\/",
    "status": "publish",
    "title": "The Best Page",
    "title_plain": "The Best Page",
    "content": "<p>This is the best page ever created.<\/p>\n<blockquote><p>Best damn page ever. – Dan<\/p><\/blockquote>\n",
    "excerpt": "This is the best page ever created. Best damn page ever. – Dan",
    "date": "2011-09-22 18:48:09",
    "modified": "2011-09-22 18:54:55",
    "categories": [],
    "tags": [],
    "author": {
      "id": 4,
      "slug": "dzachary",
      "name": "Daniel Duvall",
      "first_name": "Daniel",
      "last_name": "Duvall",
      "nickname": "Daniel Duvall",
      "url": "",
      "description": ""
    },
    "comments": [],
    "attachments": [],
    "comment_count": 0,
    "comment_status": "open",
    "translations": {
      "en": {
        "post_title": "The Best Page",
        "post_status": "publish",
        "id": 21,
        "language_code": "en",
        "is_original": true,
        "resource_id": 127
      },
      "es": {
        "post_title": "La P\u00e1gina Mejor",
        "post_status": "publish",
        "id": 22,
        "language_code": "es",
        "is_original": false,
        "resource_id": 131
      }
    },
    "language": "en"
  }
}

The language property specifies the code of the language in which the page
was written—pretty simple.

1.2. Translations

The translations objects of the same example response given in Section 1.1.
include data for each published resource that comprises a translation of
its parent object.

"translations": {
  "en": {
    "post_title": "The Best Page",
    "post_status": "publish",
    "id": 21,
    "language_code": "en",
    "is_original": true,
    "resource_id": 127
  },
  "es": {
    "post_title": "La P\u00e1gina Mejor",
    "post_status": "publish",
    "id": 22,
    "language_code": "es",
    "is_original": false,
    "resource_id": 131
  }

Properties included in each member of the translations object depend on the
type of parent object.

All post and page objects will include the following.

  • id – The ID of the translation object.
  • language_code – The code of the language in which the translation is written. Each translation object is also keyed by this value.
  • is_original – Specifies whether the language of this translation is the language in which the original work was written.
  • resource_id – The ID of the translated version of the parent object.
  • post_title – The title of the translated post/page.
  • post_status – The status of the translated post/page. Always ‘publish’.
  • post_id – Redundancy of resource_id.

All category objects will include the following.

  • id – The ID of the translation object.
  • language_code – The code of the language to which the category was translated.
  • is_original – Specifies whether the language of this translation is the language of the original category.
  • resource_id – The ID of the translated version of the parent object.
  • name – The translated category name.
  • term_id – Redundancy of resource_id.
  • post_count – The number of posts tagged with the translated category.

2. Filtering response objects by language

You may tell the API to only return objects for a specific language by using
the language parameter.

2.1. Specifying the language

The language parameter should be one of the supported language codes.

Example:

  • http://wordpress.site.example/api/get_category_index/?language=es&dev=1

2.2. Filtered results

Following is a example response to the example request in Section 2.1.

{
  "status": "ok",
  "count": 2,
  "categories": [
    {
      "id": 13,
      "slug": "noticias-de-ultima-hora-2",
      "title": "Noticias de \u00daltima Hora",
      "description": "",
      "parent": 0,
      "post_count": 1,
      "translations": {
        "en": {
          "name": "Breaking News",
          "term_id": 4,
          "post_count": 2,
          "id": 9,
          "language_code": "en",
          "is_original": true,
          "resource_id": 4
        },
        "es": {
          "name": "Noticias de \u00daltima Hora",
          "term_id": 13,
          "post_count": 1,
          "id": 26,
          "language_code": "es",
          "is_original": false,
          "resource_id": 13
        }
      },
      "language": "es"
    }
  ]
}<h3>3. Response object translation</h3>

You can request objects to be translated before they are returned. This may
save you some requests if you have the slug or ID and just need the object in
a specific language.

3.1. Specifying the target language

The target language can be specified by passing a to_language parameter. The
value should be one of the supported language codes.

Example:

  • http://wordpress.site.example/api/get_page/?slug=the-best-page&to_language=es&dev=1

3.2. Translated results

Following is an example response to the example request in Section 3.1.

{
  "status": "ok",
  "page": {
    "id": 127,
    "type": "page",
    "slug": "la-pagina-mejor",
    "url": "http:\/\/wordpress.site.example\/the-best-page\/",
    "status": "publish",
    "title": "La P\u00e1gina Mejor",
    "title_plain": "La P\u00e1gina Mejor",
    "content": "<p>Esta es la p\u00e1gina mejor se haya creado.<\/p>\n<blockquote><p>Best damn page ever. – Dan<\/p><\/blockquote>\n",
    "excerpt": "Esta es la p\u00e1gina mejor se haya creado. Best damn page ever. – Dan",
    "date": "2011-09-22 18:48:09",
    "modified": "2011-09-22 18:54:55",
    "categories": [],
    "tags": [],
    "author": {
      "id": 4,
      "slug": "dzachary",
      "name": "Daniel Duvall",
      "first_name": "Daniel",
      "last_name": "Duvall",
      "nickname": "Daniel Duvall",
      "url": "",
      "description": ""
    },
    "comments": [],
    "attachments": [],
    "comment_count": 0,
    "comment_status": "open",
    "translations": {
      "en": {
        "post_id": 127,
        "post_title": "The Best Page",
        "post_status": "publish",
        "id": 21,
        "language_code": "en",
        "is_original": true,
        "resource_id": 127
      },
      "es": {
        "post_id": 131,
        "post_title": "La P\u00e1gina Mejor",
        "post_status": "publish",
        "id": 22,
        "language_code": "es",
        "is_original": false,
        "resource_id": 131
      }
    },
    "language": "es",
    "translated": true,
    "original_slug": "the-best-page",
    "original_title": "The Best Page",
    "original_title_plain": "The Best Page"
  }
}

As you can see the slug, title, title_plain, excerpt, and content
properties have been rewritten with the Spanish translation. In addition, the
original properties have been prefixed with original_. This is always the
case for all properties except for excerpt and content. In an effort to
save on response size, the latter have been omitted.

3.3. Translatable objects and properties

Here are all of the translatable object types and their translatable
properties, those that can be rewritten as described in Section 3.2.

Objects post and page:

  • slug
  • title
  • title_plain
  • excerpt
  • content

Objects tag and category:

  • slug
  • title
  • description

Installation

  1. Upload the wpml-json-api folder to the /wp-content/plugins/ directory or install directly through the plugin installer.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress or by using the link provided by the plugin installer.

Changelog

Please see the GitHub project page for a comprehensive list of changes.

Full changelog on WordPress.org →

For developers

Is this your plugin? Show off the numbers.

Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.

Active installs badge Rating badge Health score badge

Best WPML JSON API alternatives

All api plugins →
Alternatives
Rank Plugin Active installs Rating Updated Health
1 WP Consent API WP Consent API Simple Consent API to read and register the current consent category. by Rogier Lankhorst 300K+ ★★★★★★★★★★ 5 (2) 7 days ago 80
2 Disable REST API Disable REST API Disable the use of the REST API on your website to site users. Now with User Role support! by Dave McHale 80K+ ★★★★★★★★★★ 4.8 (38) 3 years ago 37
3 Mailgun for WordPress Mailgun for WordPress Easily send email from your WordPress site through Mailgun using the HTTP API or SMTP. by Mailgun 70K+ ★★★★★★★★★★ 3.8 (49) 2 months ago 81
4 Make Connector Make Connector Make Connector. Make lets you design, build, and automate by connecting with WordPress in… by Make 70K+ ★★★★★★★★★★ 2.9 (27) 2 weeks ago 70
5 Disable WP REST API Disable WP REST API Disables the WP REST API for visitors not logged into WordPress. by Jeff Starr 30K+ ★★★★★★★★★★ 4.8 (36) 3 months ago 84
6 WP REST Cache WP REST Cache Enable caching of the WordPress REST API and auto-flush caches upon wp-admin editing. by Acato 10K+ ★★★★★★★★★★ 4.9 (42) 2 weeks ago 89
7 WPGraphQL for ACF WPGraphQL for ACF WPGraphQL for ACF seamlessly integrates Advanced Custom Fields with WPGraphQL. by Jason Bahl 10K+ ★★★★★★★★★★ 5 (1) 5 days ago 75
8 WPGet API – Connect to any external REST API WPGet API – Connect to any external REST API Connect any REST API to WordPress. WPGet API enables easy API integration, allowing you to… by David Anderson / Team Updraft 10K+ ★★★★★★★★★★ 5 (32) 3 months ago 84
9 WordPress REST API (Version 2) WordPress REST API (Version 2) Access your site's data through an easy-to-use HTTP REST API. (Version 2) by Ryan McCue 10K+ ★★★★★★★★★★ 4.2 (34) 9 years ago 43
10 WP REST API Controller WP REST API Controller Enable a UI to toggle visibility and customize properties in WP REST API requests. by Evan Herman 8K+ ★★★★★★★★★★ 4.3 (12) 4 years ago 38

FAQ

WPML JSON API: quick answers

Straight answers, pulled from live WordPress.org data.

Live data from WordPress.org · checked Nov 16, 2026

Is WPML JSON API free?

Yes. WPML JSON API is free to download and use from the official WordPress.org plugin directory.

Is WPML JSON API safe to use in 2026?

WPML JSON API shows warning signs in 2026 — compare the alternatives below before installing. It runs on 10+ sites and was last updated 14 years ago, and scores 23/100 on our health check.

How many websites use WPML JSON API?

WPML JSON API is active on 10+ WordPress websites and has been downloaded 6,440 times since it launched in September 2011. It was downloaded 156 times in the last 30 days.

Does WPML JSON API work with WordPress 7.1?

WPML JSON API is officially tested up to WordPress 3.4.2, while the latest release is 7.1.4. It may still work, but try it on a staging site first.

When was WPML JSON API last updated?

The latest version, 0.1.3, was released on December 12, 2012 (14 years ago).

Who makes WPML JSON API?

WPML JSON API is developed and maintained by dzachary.

What are the best alternatives to WPML JSON API?

The most popular alternatives to WPML JSON API are WP Consent API (300K+ installs), Disable REST API (80K+ installs) and Mailgun for WordPress (70K+ installs).

Powered by PageForge

Want thousands of pages that rank like these? Build them in an afternoon.

This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.

  • CSV, Google Sheets & API data sources
  • AI content, schema & internal links per page
  • Works with Elementor, Gutenberg, Yoast & Rank Math
  • Free on WordPress.org — no credit card
Sarah is here to help!
Hi there! 👋 Need help finding what you're looking for?
Sarah
Sarah
Online & Ready to Help
Hi there! 👋 Need help finding what you're looking for?

We'll use this to continue our conversation

Just now ✓ Verified

Join 500+ SEO Pros Scaling Their Strategy

Get exclusive programmatic SEO tactics, AI content workflows, and the latest PageForge updates delivered straight to your inbox. Stay ahead of the algorithm.

We care about your data in our privacy policy.