Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Get Use APIs · Version history

Get Use APIs changelog and version history

Latest version
2.0.17
Nov 6, 2026 (3 days ago)
Releases
75
since 2015
In the last year
11
about one every 34 days
Tested up to
WordPress 7.1.4
PHP 7.0 or later

Releases each year

  • 201519 releases
  • 20166 releases
  • 20171 release
  • 20185 releases
  • 20193 releases
  • 20206 releases
  • 20211 release
  • 20222 releases
  • 202310 releases
  • 20244 releases
  • 20258 releases
  • 202610 releases

202610 releases

  1. Get Use APIs 2.0.17Latest

    • FIX: Resolved two security issues in the block. The block now only works for Administrators and Editors; Authors and Contributors see an “access denied” message instead of a preview, and the API access token is no longer visible to non-administrators. We recommend updating. Thanks to https://github…
    • HARDENING: TLS verification no longer disabled when sending API credentials
    • CHECK: Plugin ok with WordPress “Plugin Check (PCP)” version 2.1.0.

  2. Get Use APIs 2.0.16

    • FIX: Caching-Bug fixed
    • REQUIRED: WordPress 6.9. required at least
    • CHECK: Plugin ok with WordPress 7.1
    • CHECK: Plugin compatible with WordPress “Plugin Check (PCP)” version 2.1.0.

  3. Get Use APIs 2.0.15

    • FIX: Quotation marks in HTML code within JSON data could cause broken output. Fixed.
    • FIX: replaced utf8_encode with mb_convert_encoding
    • CHECK: Plugin compatible with WordPress “Plugin Check (PCP)” version 2.0.0.

  4. Get Use APIs 2.0.14

    • IMPROVED: Characters like “%+.#@?&()[]{}|~$” are now supported in {start:ifNotEmptyAddRight:extratext}, {start:ifNotEmptyAddLeft:extratext}, {start:ifNotEmptyAdd:extratext} and {start:ifNotEmptyAddLeftRight:extratext_left##extratext_right##}. See https://doc.json-content-importer.com/json-content-i…
    • FIX: Replaced deprecated utf8_encode() with mb_convert_encoding().
    • CHECK: Plugin compatible with WordPress “Plugin Check (PCP)” version 2.0.0.

  5. Get Use APIs 2.0.13

    • IMPROVED: Now the “Allow additional HTML tags” also works for the JCI Block

  6. Get Use APIs 2.0.12

    • IMPROVED: Starting with version 2.0.11, any HTML code present in the shortcode or block is filtered to prevent dangerous code (e.g. JavaScript) from being output. However, if you want to allow certain tags or attributes as a deliberate choice: In the plugin’s “Basic Settings” there is a field calle…

  7. Get Use APIs 2.0.11

    • FIX Block: ToggleControl now working again
    • FIX: To improve security, from version 2.0.11 onward, the plugin applies additional output filtering for the Gutenberg Block, removing potentially unsafe HTML tags such as script and iframe by default. These tags may be enabled in the plugin’s basic settings if they are strictly required.

  8. Get Use APIs 2.0.10

    • FIX: removed bug causing “shortcode disabled”

  9. Get Use APIs 2.0.9

    • FIX: Improved the JCI block for apiVersion 3 — it now also should work with the Divi Builder
    • IMPROVED: To improve security, non-admin users cannot save JCI shortcodes. From version 2.0.9 onward, the plugin applies additional output filtering, removing potentially unsafe HTML tags such as script and iframe by default. These tags may be enabled in the plugin’s basic settings if they are stri…

  10. Get Use APIs 2.0.8

    • Security Issue Fixed, importaint when mbstring is not active
    • Plugin Options, Tab “Check Installation”: Added check on “mbstring and mb_check_encoding”
    • OK: Plugin ok with “Plugin Check (PCP) 1.8.0”
    • OK: Plugin ok with WordPress 6.9

20258 releases

  1. Get Use APIs 2.0.7

    • ADDED: New settings for the WordPress “Contributor” role – starting with this version, contributors can no longer request URLs or APIs. If a WordPress contributor should still be allowed to do so, an option in the “Basic Settings” can be enabled to grant this permission.

  2. Get Use APIs 2.0.6

    • BUGFIX: Handling of Form-Data at Step 1
    • REMOVED: When generating a template from the JSON data, “:datetime” was previously inserted, where applicable, to show how date and time can be formatted. Unfortunately, automatic detection of date and time values isn’t very reliable, so this feature has been removed.
    • REMOVED: In step 1, the loaded JSON is shown as a tree. An unnecessary JS library was being loaded; this has been removed.

  3. Get Use APIs 2.0.5

    • BUGFIX: Improved sanitizing Step 1, Part 2

  4. Get Use APIs 2.0.4

    • BUGFIX: Improved sanitizing Step1
    • REMOVED: The plugin’s bundled translations have been removed because translations are now provided via WordPress.org.
    • OK: Plugin ok with “Plugin Check Plugin” Version 1.6.0

  5. Get Use APIs 2.0.3

    • BUGFIX: If JSON contains numbers as values, the plugin attempts to convert them to strings. This can cause issues with certain JSON structures. Now, this conversion is only performed if the result remains valid JSON.

  6. Get Use APIs 2.0.2

    • BUGFIX: SSL-Verification
    • Plugin ok with WordPress 6.7.2
    • Plugin ok with “Plugin Check (PCP) 1.4.0”

  7. Get Use APIs 2.0.1

    • BUGFIX: CSS in the WP-Backend

  8. Get Use APIs 2.0.0

    • NEW: Create an API-Access-Set – fill form with the API-URL. select data-tye (JSON, XML, CSV) etc. Test API response and you’re ready to use the data
    • NEW: Use the API-Access-Set in Step 2: Generate a Shortcode for the data. The generatated Shortcode has all API-data, reduce it to your needs.
    • NEW: Use the API-Access-Set with the PHP function jcifree_getjson(“NAME_OF_API_ACCESS_SET”);
    • Plugin ok with WordPress 6.7.1
    • Plugin ok with “Plugin Check (PCP) 1.3.1”

20244 releases

  1. Get Use APIs 1.6.1

  2. Get Use APIs 1.6.0

  3. Get Use APIs 1.5.6

  4. Get Use APIs 1.5.5

202310 releases

  1. Get Use APIs 1.5.4

  2. Get Use APIs 1.5.3

  3. Get Use APIs 1.5.2

  4. Get Use APIs 1.5.1

  5. Get Use APIs 1.5.0

  6. Get Use APIs 1.4 .1

  7. Get Use APIs 1.4

  8. Get Use APIs 1.3.17

  9. Get Use APIs 1.3.16

  10. Get Use APIs 1.3.15

20222 releases

  1. Get Use APIs 1.3.14

  2. Get Use APIs 1.3.13

20211 release

  1. Get Use APIs 1.3.12

20206 releases

  1. Get Use APIs 1.3.11

  2. Get Use APIs 1.3.10

  3. Get Use APIs 1.3.9

  4. Get Use APIs 1.3.2

  5. Get Use APIs 1.3.8

  6. Get Use APIs 1.3.7

20193 releases

  1. Get Use APIs 1.3.6

  2. Get Use APIs 1.3.5

  3. Get Use APIs 1.3.4

20185 releases

  1. Get Use APIs 1.3.3

  2. Get Use APIs 1.3.1

  3. Get Use APIs 1.3.0

  4. Get Use APIs 1.2.20

  5. Get Use APIs 1.2.19

20171 release

  1. Get Use APIs 1.2.18

20166 releases

  1. Get Use APIs 1.2.17

  2. Get Use APIs 1.2.16

  3. Get Use APIs 1.2.15

  4. Get Use APIs 1.2.14

  5. Get Use APIs 1.2.13

  6. Get Use APIs 1.2.12

201519 releases

  1. Get Use APIs 1.2.11

  2. Get Use APIs 1.2.10

  3. Get Use APIs 1.2.9

  4. Get Use APIs 1.2.8

  5. Get Use APIs 1.2.7

  6. Get Use APIs 1.2.6

  7. Get Use APIs 1.2.5

  8. Get Use APIs 1.2.4

  9. Get Use APIs 1.2.3

  10. Get Use APIs 1.2.2

  11. Get Use APIs 1.2.1

  12. Get Use APIs 1.2.0

  13. Get Use APIs 1.1.2

  14. Get Use APIs 1.1.1

  15. Get Use APIs 1.1.0

  16. Get Use APIs 1.0.5

  17. Get Use APIs 1.0.4

  18. Get Use APIs 1.0.3

  19. Get Use APIs 1.0.2

Questions about Get Use APIs’s releases

What is the latest version of Get Use APIs?

2.0.17, released on Nov 6, 2026 (3 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.0 or later.

How often is Get Use APIs updated?

11 releases in the last year, about one every 34 days. Its first release on WordPress.org dates from January 2015.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Get Use APIs’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.