Blogs

Connect self-hosted WordPress with an application password

Connects one self-hosted WordPress site using a WordPress username and application password. siteUrl must use HTTPS and may include the path where WordPress is installed. Zernio discovers the REST API, verifies the credentials and required post/media/taxonomy capabilities, then stores the password encrypted. Create an application password in the WordPress user's profile; do not send the user's login password. Reconnecting the same site and profile updates the connection in place.

Billing: Request; paid actions are priced in credits (see GET /v1/messaging/prices) · Rate limit: 60/min

post/v1/messaging/connect/wordpress/token

Request

  • Base URL: https://apihub.co.il
  • URL: https://apihub.co.il/v1/messaging/connect/wordpress/token
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Replay-safe: the same execution is returned instead of charging twice

X-Tagstring

Group calls into one job (e.g. one video) — see GET /v1/usage?tag=…

Request body

siteUrlstring uri required

HTTPS base URL of the WordPress installation, including a subdirectory path when applicable.

usernamestring required

WordPress login name. A colon is not allowed.

applicationPasswordstring required

Application password created for the WordPress user. Spaces in WordPress display formatting are accepted.

Response

Completed

idstring

Execution id — stable across internal retries; use it with GET /v1/executions/{id}

status'pending' | 'processing' | 'completed' | 'partial' | 'failed' | 'cancelled' | 'timeout'
operationstring
tagstring nullable

Your X-Tag, if sent

created_atstring date-time
completed_atstring date-time nullable
errorstring nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.