# WordPress

Connect WordPress.com or a self-hosted WordPress site to create, schedule, update and delete articles (Blogs API), manage a WooCommerce store (Commerce API) and install ad platform tracking tags.

import { Tab, Tabs } from 'fumadocs-ui/components/tabs';

Connect a WordPress.com or self-hosted WordPress site and manage its articles with the [Blogs API](/blogs/list-blogs).

A connected account uses `platform: "wordpress"` and represents one site with one account-scoped blog.

## Quick reference

WordPress is a blog integration. The account never appears as a target in `POST /v1/posts` and has no Zernio analytics or inbox.

| Property | Value |
|----------|-------|
| Platform value | `wordpress` |
| What it manages | One site's standard posts through one account-scoped blog |
| WordPress.com auth | OAuth 2.0 |
| Self-hosted auth | Username and WordPress Application Password |
| Tracking tags | Meta, TikTok, Google, LinkedIn, Pinterest, X and OpenAI tags as theme widgets ([Tracking tags](/platforms/wordpress/tracking-pixels)) |
| Social posting | No |
| Analytics | No |
| Scheduling | Yes, native (`publishDate`; no Zernio queue) |
| Drafts | Yes (`isPublished: false`) |
| Article body | HTML (`bodyHtml`) |
| Tags | Names; missing tags are created on the site |
| Author | Numeric WordPress user ID encoded as a string |
| Featured image | Public JPEG, PNG, WebP or GIF URL; up to 10 MB |
| SEO plugin fields | Not supported |
| Pagination | Cursor (`limit` 1 to 50, default 20, plus `nextCursor`) |

## Before you start

Choose one connection path for each site:

- **WordPress.com:** the site owner approves OAuth and selects a site on WordPress.com.
- **Self-hosted WordPress:** the site owner supplies an HTTPS site URL, their WordPress login username and an Application Password created in WordPress admin.

The authenticated WordPress user must be able to publish posts and upload files. Zernio verifies both capabilities before it saves the connection. A role that can only write drafts is insufficient.

The account represents the selected site, not the person who authorized it. Connect another site as another account.

Site and article data stays on WordPress. Zernio maps it into the common Blogs API response shape.

## Connect WordPress.com

Call [`GET /v1/connect/wordpress`](/connect/get-wordpress-auth-url) with `profileId` and `redirect_url`, then send the site owner's browser to the returned `authUrl`:

The full flow, with code for every step, is on [Connect](/platforms/wordpress/connect#connect-wordpresscom).

## Connect self-hosted WordPress

In WordPress admin, the site owner opens their user profile and creates an Application Password for Zernio.

Send the generated password with the login username to [`POST /v1/connect/wordpress/token`](/connect/connect-wordpress-with-application-password):

The full flow, with code for every step, is on [Connect](/platforms/wordpress/connect#connect-self-hosted-wordpress).

## In this section

<PlatformPages platform="wordpress" />

## Related

- [Connecting accounts](/guides/connecting-accounts#wordpress): both authentication paths.
- [Blogs API](/blogs/list-blogs): the generated reference for every blog and article endpoint.
- [Get WordPress.com authorization URL](/connect/get-wordpress-auth-url): OAuth query and response fields.
- [Connect self-hosted WordPress](/connect/connect-wordpress-with-application-password): Application Password request and response fields.
- [Error handling](/guides/error-handling): canonical error envelopes and retry guidance.
- [Commerce API](/guides/commerce): WooCommerce products, stock, coupons, pages and Meta catalog sync.
- [Pixels and tracking tags](/guides/pixels): the tags you can install, per ad platform.
- [Platforms overview](/platforms): social-posting platforms and connect-only integrations.
- [WordPress REST API authentication](https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/): upstream authentication and Application Password behavior.
- [WordPress posts](https://developer.wordpress.org/rest-api/reference/posts/), [media](https://developer.wordpress.org/rest-api/reference/media/) and [tags](https://developer.wordpress.org/rest-api/reference/tags/): upstream resources behind the article mapping.