WordPress API integration guide
Publish structured posts and media to WordPress.com and Jetpack-connected sites through the same scheduler and API used for social destinations.
Publish structured posts and media to WordPress.com and Jetpack-connected sites through the same scheduler and API used for social destinations.
WordPress integration overview
Publish structured posts and media to WordPress.com and Jetpack-connected sites through the same scheduler and API used for social destinations.
The beta connector uses WordPress.com OAuth and fixed Automattic API endpoints for WordPress.com and Jetpack-connected sites; direct arbitrary self-hosted endpoints are not silently accepted.
A provider appearing in this guide does not guarantee that every operation is enabled for every account. Use capability discovery before showing a control or promising automation.
Publishing workflows
- Article title, HTML body, excerpt, slug, and post status
- Image, video, and document uploads with featured-image selection
- Numeric categories, tags, comment status, and ping status
Model a post as one parent workflow with a separate target for each WordPress account. This preserves the resolved content, delivery attempt, provider identifier, error, and retry state for every destination.
Connection and setup checklist
- 1
Configure a WordPress.com OAuth application with the exact App9 Post callback URI.
- 2
Authorize the required least-privilege scopes and select a discovered WordPress.com or Jetpack-connected site.
- 3
Verify article, media, and taxonomy capabilities before enabling each control.
Media and validation
Ready App9 Post assets are uploaded into the selected WordPress media library before the post is created. An uploaded image can become featured media while other assets are appended to the generated article body.
Validate before dispatch as well as during composition because account permissions and provider constraints can change after a draft is saved. Return target-level provider errors with a safe message, stable error code, and request ID.
Feeds, analytics, and engagement
The first beta adapter exposes publishing only. Site stats, feeds, comments, and replies remain disabled until their normalization and sync contracts are certified; WordPress has no direct-message or mention model equivalent to social networks.
Normalized analytics use null when a metric is unavailable. A missing provider metric is not the same as a measured zero, and client reports should preserve that distinction.
Frequently asked questions
Does App9 Post support every WordPress feature?
No. Support is determined by the connected account's current capability response, provider permissions, account type, provider review, and App9 Post certification status.
Should my composer hardcode WordPress limits?
No. Use the capability matrix for live validation and treat documentation as design guidance rather than a substitute for account-level constraints.
Can I use my own WordPress OAuth app?
App9 Post supports managed and customer-provided provider credentials where the provider connection is available. Customer-owned apps remain subject to the provider's review and policy requirements.