Loads translations bundled with the plugin when no language pack is installed. No API changes.<\/p>","3.6.2":"
The API now writes only as an author who is not an administrator. After updating, choose such an author (or create one) in the plugin's settings \u2014 until then nothing is published through the API.<\/p>","3.6.1":"
Renamed to WordsPost Content Publisher. No functional changes.<\/p>","3.6.0":"
Writes that check the post hasn't changed or isn't open in the editor, quiet writes, field hashes, WPML versions in other languages. SEO now reaches WPML duplicates. Existing calls answer as before.<\/p>","3.5.0":"
Texts and posts by ID in the inventory, WPML duplicates turned into translations, restore from trash, terms by ID. Trashing through the API no longer strips iframes. Existing calls answer as before.<\/p>","3.4.0":"
Site inventory, rendered SEO values, cache flush, and writes that keep foreign text intact: backslashes, SEO templates, WPML slugs and translation groups. Existing calls answer as before.<\/p>","3.3.1":"
noindex no longer follows the site-wide "Discourage search engines" setting; Read-only access to pages, WooCommerce products, product categories and menus, with each page's visible text. Existing calls answer exactly as before.<\/p>","3.2.2":" Adds a "Settings" link on the Plugins screen. No other changes.<\/p>","3.2.1":" Small fix: the new-key box no longer shows a key that has since been revoked.<\/p>","3.2.0":" Removes the site-wide primary API key. Before updating, make sure every integration uses a key of its own (created under "API keys" or via "Connect to WordsPost").<\/p>","3.1.1":" Simpler settings page: all API keys in one table with per-key actions. No API changes.<\/p>","3.1.0":" Adds revocable per-client API keys, an optional WordsPost connection and a 60\/min default rate limit. Fully compatible with 3.0: existing keys and addresses keep working.<\/p>","3.0.0":" Renamed to Content Publisher. Install it next to WP Publisher 2.x and activate it: it keeps the same API key and settings and deactivates 2.x. The old wp-publisher\/v1 address keeps working.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3771022,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3771022,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3771022,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3771290,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3771290,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["3.6.3"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[569,84,7143,23853,103],"plugin_category":[48,50],"plugin_contributors":[289203],"plugin_business_model":[],"class_list":["post-392691","plugin","type-plugin","status-publish","hentry","plugin_tags-automation","plugin_tags-media","plugin_tags-publishing","plugin_tags-rest-api","plugin_tags-wpml","plugin_category-language-tools","plugin_category-media","plugin_contributors-wordspost","plugin_committers-wordspost"],"banners":{"banner":"https:\/\/ps.w.org\/wordspost-content-publisher\/assets\/banner-772x250.png?rev=3771290","banner_2x":"https:\/\/ps.w.org\/wordspost-content-publisher\/assets\/banner-1544x500.png?rev=3771290","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/wordspost-content-publisher\/assets\/icon.svg?rev=3771022","icon":"https:\/\/ps.w.org\/wordspost-content-publisher\/assets\/icon.svg?rev=3771022","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n WordsPost Content Publisher adds a REST API ( Everything works without any external service. Optionally, the settings page has a \"Connect to WordsPost\" button for the WordsPost content service (https:\/\/wordspost.com): it gives WordsPost its own revocable key after you approve it on a confirmation screen, instead of copying the key by hand. Nothing is sent to WordsPost unless you start the connection and press \"Allow\" \u2014 see External services below.<\/p>\n\n The full REST API reference, curl examples and a Postman collection are in the plugin's The plugin itself never sends a request to any external service. Two things involve other sites:<\/p>\n\n When an authenticated API caller passes an address in the WordsPost (https:\/\/wordspost.com) is a content service that writes and publishes posts to connected sites through this plugin's API. Connecting it is optional and happens only when a site administrator starts it:<\/p>\n\n From then on WordsPost uses that key to create, edit and delete posts and media, as the confirmation screen states. You can revoke it at any time with \"Disconnect\" on the settings page. \"Cancel\" on the confirmation screen sends WordsPost only a refusal.<\/p>\n\n WordsPost terms of use: https:\/\/wordspost.com\/terms\/\nWordsPost privacy policy: https:\/\/wordspost.com\/privacy-policy\/<\/p>\n\n\n Content Publisher is the new name of WP Publisher. WordPress sees it as a separate plugin, so:<\/p>\n\n Delete WP Publisher.<\/p><\/li>\n Create a new API key under \"API keys\" and put it into your integration: since 3.2 the old site-wide key is not carried over.<\/p><\/li>\n<\/ol>\n\n The old address No. The plugin is complete on its own: any system that can send HTTP requests (your own script, an automation tool) can publish through it with an API key. The WordsPost button is optional and does nothing until you use it.<\/p><\/dd>\n Rank Math and Yoast SEO. If neither is active, requests that include an No. Without WPML the site is treated as monolingual: Every request carries an API key in a header. Keys are stored only as SHA-256 hashes, so the site never keeps them in readable form \u2014 which is also why a key is shown only once. Reissue or revoke any key at any time from the settings page; the old value stops working immediately.<\/p>\n\n Everything the API writes is written as the post author chosen in the plugin's settings, which must be a user who can write posts but cannot administer the site \u2014 an Editor, for example. Administrators are not accepted, so a key can never change the site's settings, users, plugins or themes. The settings page (and the \"Connect to WordsPost\" screen) can create such an Editor for you, under a name you choose; until one is chosen, nothing is published through the API.<\/p>\n\n A key is a powerful credential: it can publish and delete posts, and read the site's content \u2014 posts, pages, products and the other public post types, including drafts, private and password-protected ones, pages a membership plugin hides from visitors and, by ID, posts in the trash. It can also restore posts from the trash (republishing what was published), turn WPML duplicates into translations and make WPML versions of posts in other languages. Give a key only to a service you trust as you would an editor of the site.<\/p><\/dd>\n No. It never turns on automatic updates for itself; updates happen only when a site administrator installs them.<\/p><\/dd>\n\n<\/dl>\n\n\nGET \/ping<\/code> reports it as search_engines_discouraged<\/code>.<\/p>","3.3.0":"content-publisher\/v1<\/code>) that lets an external system create, update, delete and search posts, upload and manage media, manage categories and tags, set SEO fields and, when WPML is active, manage post languages and translation links. It can also read the rest of the site \u2014 pages, WooCommerce products, product categories and menus \u2014 so the external system can see what the site is about and link to it, and list the whole site's content in a light inventory, so the external system can keep its own copy in sync. Every request is authenticated with an API key. Each client gets its own key \u2014 created on the plugin's settings page, or obtained by a service through a confirmation screen \u2014 and every key can be renamed, reissued or revoked on its own.<\/p>\n\nFeatures<\/h4>\n\n
\n
date<\/code> + future<\/code>), comments, auto excerpt, auto table of contents (from H2\/H3 headings), mobile-friendly table wrapping with an optional card layout on narrow screens, and Cyrillic-to-Latin slug transliteration (Russian and Ukrainian)<\/li>\nrequest_key<\/code> with POST \/posts<\/code> or POST \/media<\/code> and a repeated request returns the item created the first time instead of a duplicate, even when two copies arrive at once or the first one was interrupted halfway<\/li>\n%date%<\/code>, %%title%%<\/code>), plus the title and description a search engine actually gets after the templates are applied<\/li>\n\/languages<\/code> endpoint listing what the site speaks; with WPML, post language and translation-group linking via lang<\/code> \/ translation_of<\/code>, a translations<\/code> map on every post, filters to find posts that still need translating, and a clear 409<\/code> instead of a duplicate when a language in the group is already taken; translations keep their original's slug, change language within their group, and can take the place of a WPML duplicate<\/li>\nX-RateLimit-*<\/code> headers<\/li>\ndocs\/<\/code> folder (API.md<\/code>, openapi.yaml<\/code>, postman_collection.json<\/code>).<\/p>\n\nExternal services<\/h3>\n\n
Image downloads requested by your API client<\/h4>\n\n
url<\/code> field of POST \/media<\/code>, the file at that address is fetched once with WordPress's own download_url()<\/code> and stored in the media library. Which addresses are fetched is entirely up to the site's own API client; nothing about the site or its visitors is sent. Uploads sent as inline data<\/code> involve no outgoing request at all.<\/p>\n\nCache plugins, when your API client asks for a flush<\/h4>\n\n
POST \/cache\/flush asks the cache plugin installed on the site to clear its cache, through that plugin's own functions. The plugin sends nothing anywhere itself; if the cache plugin is set up to purge a CDN as well, it does so on its own, as it would when you clear the cache from its screen.\n<\/code><\/pre>\n\nWordsPost (optional, only when you connect it)<\/h4>\n\n
\n
\n
\/wp-content\/plugins\/<\/code>, or install the zip through Plugins \u2192 Add New \u2192 Upload Plugin.<\/li>\nAuthorization: Bearer <key><\/code> header with every request (X-WPPUB-Api-Key: <key><\/code> works the same way).<\/li>\n<\/ol>\n\nUpgrading from WP Publisher 2.x<\/h4>\n\n
\n
wp-publisher\/v1<\/code> keeps working in every 3.x version; move integrations to content-publisher\/v1<\/code> when convenient.<\/p>\n\n\n\n
Do I need WordsPost to use this plugin?<\/h3><\/dt>\n
Which SEO plugins are supported?<\/h3><\/dt>\n
seo<\/code> field are rejected with a clear error rather than silently discarding the data.<\/p><\/dd>\nDoes it require WPML?<\/h3><\/dt>\n
\/languages<\/code> returns WordPress's own locale with multilingual: false<\/code>, and posts report that language. The lang<\/code> and translation_of<\/code> fields are still accepted but have no effect.<\/p><\/dd>\nHow is the API secured?<\/h3><\/dt>\n
Does the plugin update itself automatically?<\/h3><\/dt>\n
3.6.3<\/h4>\n\n
\n
3.6.2<\/h4>\n\n
\n
409 wppub_author_not_allowed<\/code> and the dashboard says so. The settings page and the \"Connect to WordsPost\" screen can create such an Editor, named as you like (\"WordsPost\" by default).<\/li>\n3.6.1<\/h4>\n\n
\n
wordspost-content-publisher<\/code>). Nothing else changes: settings, keys and the REST API stay as they were.<\/li>\n<\/ul>\n\n3.6.0<\/h4>\n\n
\n
if_hash<\/code> on PUT \/posts\/{id}<\/code> and POST \/posts\/{id}\/unduplicate<\/code>: the write goes through only if the post's inventory hash<\/code> is still the one given \u2014 otherwise 409 wppub_changed<\/code> with the current one, nothing written. The comparison and the write happen under a row lock, so of concurrent writes with one if_hash<\/code> exactly one succeeds.<\/li>\nrespect_lock<\/code>: 409 wppub_locked<\/code> while someone has the post open in the editor.<\/li>\nquiet<\/code> on POST \/posts<\/code>, PUT \/posts\/{id}<\/code> and duplicate-to<\/code>: no pingbacks and no enclosure fetching for that write.<\/li>\nfield_hashes=1<\/code> in the inventory: the MD5 of title, content and excerpt as separate fields.<\/li>\nPOST \/posts\/{id}\/duplicate-to<\/code>: a version of the post in another language made by WPML's own duplication, turned straight into an ordinary translation; the SEO canonical address is not carried over.<\/li>\nunfiltered_html<\/code> in GET \/ping<\/code> and in the inventory's env<\/code>: whether texts are stored as sent.<\/li>\nPUT \/posts\/{id}<\/code> with seo<\/code> now writes the SEO fields before saving the post, so WPML duplicates get the new title and description along with the new text; if the save fails, they go back to what they were (both base paths).<\/li>\nPUT \/posts\/{id}<\/code> are written before the post is saved, so WPML duplicates get them right away; they go back to what they were if the save fails (both base paths).<\/li>\ncontent-publisher\/v1<\/code> only; responses without them are as in 3.5.0, apart from unfiltered_html<\/code>.<\/li>\n<\/ul>\n\n3.5.0<\/h4>\n\n
\n
GET \/inventory?kind=texts<\/code>: raw title, content and excerpt by id cursor, up to 500 per page and about 8 MB, at a fixed number of database queries per page, with the same hash<\/code> as kind=posts<\/code>.<\/li>\nids=<\/code> in kind=posts<\/code> and kind=texts<\/code>: those posts, trashed ones included, and missing_ids<\/code> for the ones that no longer exist.<\/li>\nenv<\/code> block in the inventory: WPML, the installation, the post types and taxonomies covered and which of them WPML translates.<\/li>\nPOST \/posts\/{id}\/unduplicate<\/code> turns a WPML duplicate into an ordinary translation without changing it; POST \/posts\/{id}\/restore<\/code> brings a post back from the trash into its previous status.<\/li>\ncategories<\/code> and tags<\/code> accept {\"id\": N}<\/code>; PUT<\/code> of a category or tag accepts translation_of<\/code> to link it into a translation group.<\/li>\ncontent-publisher\/v1<\/code> only; responses without the new parameters are as in 3.4.0, apart from env<\/code> on the first page of the inventory.<\/li>\n<\/ul>\n\n3.4.0<\/h4>\n\n
\n
GET \/inventory?kind=posts|terms|menus<\/code>: the whole site's content a page of up to 5000 items at a time, by id cursor, at a fixed number of database queries per page \u2014 WPML language, translation group and duplicate flag, page builder, former slugs, featured image and a hash<\/code> fingerprint for posts; language and group for terms and menus; site_time_gmt<\/code> as the \"changed since\" marker.<\/li>\ndate_created_gmt<\/code> and date_modified_gmt<\/code>.<\/li>\nwith_seo_rendered=1<\/code> adds the SEO title and description as search engines get them (Rank Math, Yoast).<\/li>\n%date%<\/code>; an automatic excerpt leaves shortcodes out.<\/li>\nPUT<\/code> with lang<\/code> moves a post within its translation group instead of taking it out, answers 409<\/code> when the language is taken, and detach: true<\/code> takes it out; replace_duplicate<\/code> writes a translation into a WPML duplicate; new categories take a parent<\/code>, and a second translation into a taken language is a 409<\/code>.<\/li>\nPOST \/cache\/flush<\/code>.<\/li>\nsource_lang<\/code> (the language WPML records them as translated from) and translation_jobs<\/code> (open WPML translation jobs in their group); GET \/languages<\/code> adds wpml_auto_translate<\/code> (WPML's automatic translation mode and post types), so an integration can stay out of what WPML translates by itself.<\/li>\ncontent-publisher\/v1<\/code> only (the term fix applies everywhere); without the new parameters responses are the same as in 3.3.1, apart from the two new dates.<\/li>\n<\/ul>\n\n3.3.1<\/h4>\n\n
\n
noindex<\/code> now reflects only the item itself \u2014 its SEO settings, its post type's default, a status other than published, or being a WooCommerce cart\/checkout\/account page \u2014 and no longer the site-wide \"Discourage search engines\" setting, which made every item of a site under development look the same. That setting is reported on its own as search_engines_discouraged<\/code> in GET \/ping<\/code>.<\/li>\n<\/ul>\n\n3.3.0<\/h4>\n\n
\n
GET \/posts?type=page|product<\/code> and GET \/posts\/{id}?type=\u2026<\/code>, with page fields (parent, order, template, front page, posts page) and product fields (categories, SKU, stock, catalog visibility). Writing is still for blog posts only.<\/li>\nwith_text=1<\/code> adds text<\/code>: the content as a visitor reads it \u2014 rendered like the site's front end (blocks, shortcodes, Elementor, WPBakery), then reduced to plain text of up to 3000 characters. Embeds are not fetched while doing so.<\/li>\nmodified_after<\/code> returns only what changed since a given moment.<\/li>\ntype<\/code>, password-protected items are left out, seo.robots<\/code> shows the robots rules that actually apply (including Rank Math's and Yoast's post type defaults), and a new noindex<\/code> flag sums them up.<\/li>\nGET \/terms?taxonomy=category|post_tag|product_cat<\/code> with each term's link, description and parent, and hide_empty<\/code>.<\/li>\nGET \/menus<\/code>: menus in theme locations and unassigned ones, per WPML language.<\/li>\nGET \/ping<\/code> adds tagline<\/code>, front_page_id<\/code>, posts_page_id<\/code> and woocommerce<\/code>, and five new features<\/code>.<\/li>\ncontent-publisher\/v1<\/code> only; without the new parameters every response is the same as in 3.2.<\/li>\n<\/ul>\n\n3.2.2<\/h4>\n\n
\n
3.2.1<\/h4>\n\n
\n
DELETE \/keys\/self<\/code>) while its value is still shown in the \"new key\" box, the box disappears, so a dead key can't be copied by mistake. A reissue also removes the old value from other administrators' boxes.<\/li>\n<\/ul>\n\n3.2.0<\/h4>\n\n
\n
DELETE \/keys\/self<\/code> works for every key (the wppub_primary_key<\/code> error no longer exists). The primary<\/code> field of a key description is always false<\/code>.<\/li>\n3.1.1<\/h4>\n\n
\n
3.1.0<\/h4>\n\n
\n
GET \/connect\/info<\/code> and POST \/connect\/exchange<\/code> (public), GET \/keys\/self<\/code> and DELETE \/keys\/self<\/code>.<\/li>\nX-RateLimit-Limit<\/code>, X-RateLimit-Remaining<\/code>, X-RateLimit-Reset<\/code> headers plus Retry-After<\/code> on 429.<\/li>\nGET \/ping<\/code> also reports rate_limit<\/code>, key<\/code>, home_url<\/code>, install_id<\/code> and rest_root<\/code>; new features keys<\/code>, connect<\/code>, rate_headers<\/code>.<\/li>\n3.0.0<\/h4>\n\n
\n
content-publisher<\/code>). New REST address content-publisher\/v1<\/code>; the 2.x address wp-publisher\/v1<\/code> keeps working throughout 3.x.<\/li>\n