Connect WordPress or a WordPress-Compatible Blog

VibeCom publishes blog posts through the WordPress REST API shape. You can connect a normal WordPress site, or you can implement the same small API surface on your own blog and use it as a custom publishing endpoint.

Option A: Connect a WordPress Site

Use this if your blog runs on WordPress 5.6 or later.

1. Create an Application Password

In WordPress:

1. Open Users → Profile
2. Scroll to Application Passwords
3. Enter a name like VibeCom
4. Click Add New Application Password
5. Copy the generated password immediately

If the Application Passwords section is missing, check that your site uses HTTPS and is running WordPress 5.6+.

2. Create a Blog Channel

In VibeCom:

1. Open Growth Autopilot
2. Go to Channels
3. Create a channel with platform Blog
4. Open the Blog channel settings
5. Click Connect WordPress

Enter:

VibeCom tests the connection by calling:

GET https://myblog.com/wp-json/wp/v2/users/meAuthorization: Basic base64(username:application_password)

If the response is successful, VibeCom stores the site URL and encrypted credentials for that Blog channel.

Option B: Build Your Own Blog Endpoint

Use this if your blog is not WordPress, but you want VibeCom to publish to it.

Your server only needs to expose two WordPress-compatible endpoints:

The base URL you enter in VibeCom must be public and reachable by VibeCom, for example:

https://blog.example.com

VibeCom will call:

https://blog.example.com/wp-json/wp/v2/users/mehttps://blog.example.com/wp-json/wp/v2/posts

Localhost, private network URLs, and .local / .internal hosts are blocked for production publishing.

Authentication

VibeCom uses HTTP Basic Auth, matching WordPress Application Passwords.

When you connect the Blog channel, VibeCom stores:

base64(username:application_password)

Every validation and publish request includes:

Authorization: Basic <base64(username:application_password)>

For a custom blog endpoint, treat the username as an account identifier and the application password as an API key. Return 401 if the credentials are invalid.

Validate Endpoint

Implement:

GET /wp-json/wp/v2/users/meAuthorization: Basic <credentials>

Successful response:

{  "id": 1,  "name": "Your Blog",  "slug": "your-blog"}

Optional avatar response:

{  "id": 1,  "name": "Your Blog",  "slug": "your-blog",  "avatar_urls": {    "48": "https://blog.example.com/avatar-48.png",    "96": "https://blog.example.com/avatar-96.png"  }}

VibeCom uses this endpoint only to confirm that the channel can publish.

Publish Endpoint

Implement:

POST /wp-json/wp/v2/postsAuthorization: Basic <credentials>Content-Type: application/json

Request body:

{  "title": "How we launched the new dashboard",  "content": "<p>HTML content generated from the approved VibeCom post.</p>",  "status": "publish",  "excerpt": "Short summary for previews and meta descriptions.",  "cover_image": "https://cdn.example.com/cover.png",  "tags": ["launch", "product-update", "founder-led-growth"]}

Fields:

Successful response:

{  "id": 123,  "link": "https://blog.example.com/blog/how-we-launched-the-new-dashboard",  "status": "publish",  "title": {    "rendered": "How we launched the new dashboard"  }}

VibeCom reads:

Return 201 Created for a successful publish.

Example cURL Test

Replace the username, API key, and domain:

curl -i https://blog.example.com/wp-json/wp/v2/users/me \  -u "vibecom:YOUR_BLOG_API_KEY"

Publish a test post:

curl -i https://blog.example.com/wp-json/wp/v2/posts \  -u "vibecom:YOUR_BLOG_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "title": "VibeCom test post",    "content": "<p>This is a test post from VibeCom.</p>",    "status": "publish",    "excerpt": "Testing VibeCom blog publishing.",    "tags": ["vibecom", "test"]  }'

Minimal Next.js Route Example

This mirrors the API shape VibeCom expects:

import { NextResponse } from "next/server";
const BLOG_API_KEY = process.env.BLOG_API_KEY;
function isAuthorized(request: Request) {  const auth = request.headers.get("authorization");  if (!auth?.startsWith("Basic ")) return false;
  const decoded = Buffer.from(auth.slice(6), "base64").toString("utf8");  const [, password] = decoded.split(":");  return Boolean(BLOG_API_KEY && password === BLOG_API_KEY);}
export async function GET(request: Request) {  if (!isAuthorized(request)) {    return NextResponse.json(      { code: "invalid_credentials", message: "Invalid credentials" },      { status: 401 },    );  }
  return NextResponse.json({    id: 1,    name: "My Blog",    slug: "my-blog",  });}

For POST /wp-json/wp/v2/posts, save title, content, excerpt, cover_image, and tags into your blog database, then return the published URL in link.

Error Responses

Use WordPress-style JSON errors where possible:

{  "code": "invalid_credentials",  "message": "Invalid credentials"}

Recommended status codes:

VibeCom displays non-2xx responses in the publish error message, so keep the response body short and actionable.

Troubleshooting

Security Notes

• Use HTTPS.
• Store the application password or API key hashed if you control the receiving blog.
• Create a dedicated publishing user or API key for VibeCom.
• Revoke the key from your blog if you disconnect the channel.
• Do not expose this endpoint without authentication.

Next Steps

• Channels & Platforms — Understand Blog channels
• Auto-Publish — How approved posts are published
• Your First Content Batch — Generate your first blog post