Contesimal

wondermentapps

Contesimal Connector adds REST API endpoints to your WordPress site, allowing external applications to create and manage content using an API key.

Requests are made to your site’s <code>/wp-json/contesimal/v1/</code> endpoints. The plugin does not send any data externally on its own.

External services and privacy

<ul>
<li>Service: Designed to work with Contesimal (https://contesimal.ai), but compatible with any client using your API key.</li>
<li>Data received: Post title, content (HTML), excerpt, status, categories, tags, post type, author ID, and media URLs. The optional users endpoint returns public-style author fields (ID, display name, slug) for users who can edit posts—no passwords or email.</li>
<li>Media handling: Your WordPress site may download remote files from provided URLs to create Media Library attachments.</li>
<li>When: Only when a valid API request is sent to your site. No background communication occurs.</li>
<li>Control: External access is enabled only if you share the API key. You can regenerate the key or deactivate the plugin at any time.</li>
<li>Consent: By enabling the plugin and sharing the API key, the site administrator allows external applications to submit content.</li>
</ul>

Authentication

All endpoints require an API key sent in the <code>X-API-Key</code> header (or <code>Authorization: Bearer</code>).

The key is:
– Generated on your site
– Stored as a secure hash
– Managed by administrators only

Requests without a valid key are rejected (401). Rate limiting is applied per IP.

API keys should be treated as sensitive credentials and only shared with trusted systems.

Features

<ul>
<li>API key authentication (hashed storage)</li>
<li>Create posts via REST API</li>
<li>List categories, post types, and author-capable users (IDs for <code>author_id</code>)</li>
<li>Media import from external URLs</li>
<li>Rate limiting (per IP)</li>
<li>Configurable CORS</li>
<li>Optional request logging (admin only)</li>
</ul>

REST endpoints (base: <code>/wp-json/contesimal/v1</code>)

<ul>
<li><code>GET /ping</code> – Health check</li>
<li><code>GET /categories</code> – List categories</li>
<li><code>GET /post-types</code> – List public post types</li>
<li><code>GET /users</code> – List users with <code>edit_posts</code> (optional <code>session_only</code>, <code>search</code>, <code>limit</code>)</li>
<li><code>GET /posts</code> – List posts by post type with pagination and total count</li>
<li><code>POST /publish</code> – Create post</li>
<li><code>POST /media/import</code> – Import media from URLs</li>
</ul>

An admin notice is shown when API access is enabled, indicating that external publishing is active.

<h3>REST API Reference</h3>

All endpoints require: <code>X-API-Key: your_api_key</code>

<h4>GET /wp-json/contesimal/v1/ping</h4>

Returns plugin status.

Response:
{ “status”: “ok”, “plugin”: “contesimal-connector”, “version”: “1.0.0” }

<h4>GET /wp-json/contesimal/v1/categories</h4>

Returns category list.

<h4>GET /wp-json/contesimal/v1/post-types</h4>

Returns public post types.

<h4>GET /wp-json/contesimal/v1/users</h4>

Returns users who can author posts (<code>edit_posts</code>), suitable for <code>author_id</code> on <code>POST /publish</code>.

Query parameters (all optional):




 Parameter
 Description




 search
 Substring match on login, nicename, or display name


 session_only
 <code>1</code> to only include users with stored WordPress session tokens (typically logged in recently)


 limit
 Max results, 1–200 (default 200)




Response (example):
{ “success”: true, “users”: [ { “id”: 1, “name”: “Site Admin”, “slug”: “admin” } ] }

<h4>GET /wp-json/contesimal/v1/posts</h4>

Returns a paginated list of posts for a given post type, plus the total count for that filter.

Query parameters (all optional):




 Parameter
 Description




 post_type
 Public post type (default <code>post</code>)


 per_page
 1–100, default 50


 offset
 Number of posts to skip (default 0)


 status
 Comma-separated status list (default <code>publish</code>), or <code>any</code>


 search
 Optional keyword across title/content




Response (example):
{ “success”: true, “post_type”: “post”, “total”: 124, “per_page”: 50, “offset”: 0, “count”: 50, “posts”: [ { “post_id”: 42, “title”: “Hello world”, “slug”: “hello-world”, “status”: “publish”, “date”: “2026-05-14T11:50:00+00:00”, “author_name”: “Site Admin”, “link”: “https://example.com/hello-world/”, “featured_image”: “https://example.com/wp-content/uploads/2026/05/cover.jpg”, “featured_image_id”: 99, “categories”: [ “News”, “Updates” ], “tags”: [ “Announcement”, “WordPress” ], “content”: “

Hello

” } ] }

<h4>POST /wp-json/contesimal/v1/publish</h4>

Creates a post.

Headers:
Content-Type: application/json 
X-API-Key: your_api_key

Body:




 Field
 Type
 Required
 Description




 title
 string
 Yes
 Post title


 content
 string
 Yes
 HTML content


 status
 string
 No
 publish, draft, pending, private


 excerpt
 string
 No
 Post excerpt


 post_type
 string
 No
 Default: post


 category_ids
 array
 No
 Category IDs


 tags
 array
 No
 Tag names


 featured_image_url
 string
 No
 Image URL


 author_id
 integer
 No
 Default: 1




Responses:
– 200 Success
– 400 Bad request
– 401 Invalid API key
– 429 Rate limit exceeded
– 500 Server error

Contesimal Connector

Publish content to WordPress from external applications via a secure REST API using API key authentication.

rATRIJS

Since version 3.1 WordPress has it’s own implementation of custom post type archives so you can create them without this plugin – visit this page for more info -> https://codex.wordpress.org/Post_Types. Nevertheless I do believe that this plugin is more flexible and you can still use it and it will still work as expected.
This plugin will enable custom post type archives (also yearly, monthly and daily) together with feeds, customizable titles and paging.
These archives will work the same way as the category or tag archives work when you go to, for example, http://example.com/category/example.
WordPress 3.0 new custom post type feature is awesome. The only problem is – it lacks archive functionality for these post types so you can’t easely assign one URL to just list your ‘photo’ post type posts. You also won’t be able to get feeds just from this post type. This plugin adds this functionality to WordPress so that you can fully enjoy custom post types. It will also let you to create seperate templates for your post type archives which wasn’t possible before. You will be able to use the same things you are familiar with if you are a theme developer as well as you will be able to enjoy this feature if you are not a developer but just want to enable this feature for your blog.
With this plugin you will be able to specify:
<ul>
<li>URL base for custom post types. Assuming you have a post type named ‘photo’, you can list all your post types in URL http://example.com/photo or http://example.com/post-type/photo – whatever you like by simply filling one field.</li>
<li>Whether to use the custom post type rewrite slug or custom post type name as URL parameter after ‘URL base’. It defaults to true, because that’s the way it should work, but it might be more efficient to disable this option. For more information please read the FAQ. Also if this option is enabled then you will be able to specify a custom rewrite slug for each enabled custom post type archive.</li>
<li>Title for post type archives. You can use {POST_TYPE_NAME} and {POST_TYPE_SINGULAR_NAME} variables into this option. {POST_TYPE_NAME} will be replaces with current post types name and {POST_TYPE_SINGULAR_NAME} will be replaces with current post types singular name. So if you are in post type ‘photo’ and this option is set to ‘Post Type “{POST_TYPE_SINGULAR_NAME}”‘ then the title will say ‘Post Type “Photos”‘. You can also use {SEP}, {SEP_LEFT_SPACE}, {SEP_RIGHT_SPACE}, {SEP_SPACED}. These will be replaced with seperator specified in wp_title function. Spaced ones will have the space on defined side. {SEP_LEFT_SPACE} will have space in left side and vice verca. {SEP_SPACED} will have spaced on both sides. I had to do this in this way, because WordPress trims variables before saving. If left blank (this option), plugin won’t change the title. You can also specify a custom title for each enabled custom post type archive.</li>
<li>What template file to use for rendering a custom post type. You can use either one template for all post types or just type ‘post-type-{POST_TYPE}.php’ and for post type ‘photo’ plugin will try to include ‘post-type-photo.php’ to render the custom post type.</li>
<li>What template file to load if above template file is not found. So it’s easy to use index.php for all post types except ‘photo’ for example.</li>
<li>Whether to add a feed link for custom post type archive. Will work the same way as any other feed links, for example in category index pages where your visitors can subscribe to your site updates. Plugin will automatically insert the feed link if <a href="https://codex.wordpress.org/Function_Reference/add_theme_support" rel="nofollow ugc">‘automatic-feed-links’</a> is enabled for your theme. If that’s true then plugin won’t show this option in plugin settings.</li>
<li>Post types that gets archives. Just tick the checkboxes next to those post types you want to see archives. Easy as that.</li>
</ul>
Note that if you update URL base field, disable/enable post type rewrite tag usage or enable/disable some post type archives, then you will have to visit ‘Permalinks’ section under ‘Settings’ to flush old permalinks and enable the changes.
Also a good thing for theme developers – you have four new functions to use:
<ul>
<li>pta_is_post_type_archive – this function will work similary as is_category or is_single and so on. It will return true if this page is a custom post type archive or false if it isn’t. You can also specify an optional argument with post type name and then function will return boolean to say whether you’re in post type archive for that post type or not. Simple and useful!</li>
<li>get_the_post_type_permalink – this function will return a link to custom post type archive for current post in the WordPress loop. Or you can specify a post type slug or post ID or post object as an argument if you are not in a loop. In this way you can always link to custom post type archives wherever you are.</li>
<li>the_post_type_permalink – uses get_the_post_type_permalink to echo the link rather than return it.</li>
<li>wp_get_post_type_archives – will work the same way as <a href="https://codex.wordpress.org/Function_Reference/wp_get_archives" rel="nofollow ugc">‘wp_get_archives’</a> function that allows you to get yearly, monthly, daily (and so on) archives for custom post types.</li>
</ul>
If you have any issues at all, please try these steps that hopefully will help you:
<ul>
<li>check out the Faq section to search for an answer for your question</li>
<li>visit plugins homepage (http://ratvars.com/custom-post-type-archives) for more information (you can also leave a comment there)</li>
<li>create a new forum topic in here about the issue you’re having</li>
</ul>
I will try to help you as good as I can.

Custom Post Type Archives

Enables custom post type archives that will support both paging and feeds. All fully customizable.

Contesimal Connector vs Custom Post Type Archives