WordPress Integration & Automated REST Sync
Complete guide to connecting self-hosted WordPress sites via native REST API and Application Passwords for 1-click article publishing.
Overview
Unlike legacy social tools that require bloated third-party plugins that degrade site speed, HyperFast communicates directly with the official WordPress REST API built into WordPress Core. You can publish breaking news stories, scheduled blog posts, and multi-channel campaigns with automated featured photography and category tags in one click.
Step-by-Step Instructions
Verify WordPress REST API Access
Open `https://your-domain.com/wp-json/` in a browser. It should return a JSON response confirming that the WordPress REST API is active and unblocked by firewalls.
Generate WordPress Application Password
Log in to your WordPress Admin dashboard. Navigate to Users > Profile (or Users > All Users > Edit User). Scroll down to the 'Application Passwords' section. Enter 'HyperFast' in the 'New Application Password Name' field, and click 'Add New Application Password'.
Copy the Generated 24-Character Token
WordPress will display a 24-character password token (e.g. `abcd efgh ijkl mnop qrst uvwx`). Copy this token immediately, as it cannot be viewed again.
Connect WordPress in HyperFast
In HyperFast, go to Connected Channels > Add Channel (or Workspace > Integrations > WordPress). Enter your Site URL (e.g. `https://yourdomain.com`), your WordPress Username, and paste the 24-character Application Password token. Click 'Test & Connect'.
Configure Authors, Categories & Default Status
Once connected, HyperFast automatically retrieves your WordPress categories and authors. Select your default publishing author, default category mapping, and whether incoming articles should publish as 'Live' or 'Draft'.
WordPress REST API Integration Specifications
| Integration Aspect | Technical Requirement / Endpoint | HyperFast Handling | Notes |
|---|---|---|---|
| WordPress Version | WordPress 5.6 or higher | Fully compatible with all modern WP releases | Works on Apache, Nginx, LiteSpeed |
| Authentication | Application Passwords (RFC 7617) | 24-character encrypted auth token | No admin password sharing needed |
| Posts Endpoint | /wp-json/wp/v2/posts | POST request with rendered HTML content | Supports custom slugs and categories |
| Media Endpoint | /wp-json/wp/v2/media | Direct multipart binary image upload | Sets alt text and assigns featured_media ID |
| SSL / Security | HTTPS (SSL Certificate Required) | Mandatory TLS encryption on all requests | Prevents credential interception |
Prerequisites & Preparation
- Ensure your WordPress site is running on HTTPS with a valid SSL certificate.
- Verify that pretty permalinks are enabled in WordPress Admin > Settings > Permalinks (e.g. 'Post name').
- Have Administrator or Editor level credentials on the target WordPress installation.
Troubleshooting & Edge Cases
401 Unauthorized error when testing connection
Check if your Apache/Nginx server is stripping authorization headers. Add `RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]` to your `.htaccess` file, or ensure security plugins like Wordfence are not blocking Basic Authentication.
Featured images fail to upload
Verify that your `/wp-content/uploads/` directory has write permissions (755 or 775) and that PHP `upload_max_filesize` is at least 10MB.
403 Forbidden response from Cloudflare
If using Cloudflare, create a WAF bypass rule allowing requests from HyperFast user agents to `/wp-json/*`.