Create post with the WordPress.com API

Creates a post or page and returns it. The default status is publish, which puts it live right away: send draft to save it unpublished. Once published, it is also shared on the social accounts connected to the site, unless publicize is false.

Identifier
wordpress_com_create_post

The request

POST https://connect.reportei.com/api/tools/wordpress_com_create_post/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "site": "<site>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
sitestringYesID of the site, from List sites, or its domain, like example.wordpress.com.
typestringNopost, the default, or page.Values: post, page
titlestringNoTitle of the post.
contentstringNoContent of the post, in HTML.
excerptstringNoShort summary of the post.
statusstringNopublish, the default, puts the post live; draft saves it unpublished; pending waits for review; private publishes it only for the site members; future schedules it for date.Values: publish, draft, pending, private, future
datestringNoDate of the post. With status future, the moment it goes live.
categoriesstringNoComma-separated category names or IDs, from List categories.
tagsstringNoComma-separated tag names.
slugstringNoPart of the URL of the post.
publicizebooleanNofalse keeps the post from being shared on the social accounts connected to the site. The default is true.
publicize_messagestringNoCustom message for the social share.

Supported connections

Your customer connects their WordPress.com account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/wordpress_com, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/wordpress_com_create_post. It becomes your agent's tool definition with no conversion.

Other WordPress.com tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.