Get WordPress.com OAuth connect URL
Initiates OAuth for a WordPress.com site or a Jetpack-connected site.
WordPress is a connect-only blog platform: the connected account powers
the Blogs API (/v1/accounts/{accountId}/blogs) and does not support
social posts, inbox, analytics, ads, or Shopify product operations.
Redirect the user to authUrl; after authorization, WordPress returns
the browser to Zernio's internal callback and Zernio redirects to
redirect_url (or the dashboard when omitted). Reconnecting the same
site and profile updates the stored connection in place. The consent
request omits scope to use WordPress.com's default single-site grant.
Granular scopes cannot access the /wp/v2 article API. Zernio checks
that API before saving the connection and does not request explicit
global authorization across all sites.
API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Query Parameters
Your Zernio profile ID (get from /v1/profiles).
Custom redirect after connection. Must be an absolute http(s) URL or custom app scheme such as myapp://callback; relative and unsafe URLs return 400.
Response Body
application/json
application/json
application/json
{ "authUrl": "http://example.com", "state": "string"}Connect a Shopify store with a custom-app Admin token
Token-paste alternative to the OAuth flow: connect a store using the Admin API access token of a custom app the merchant created in their own Shopify admin (Settings → Apps and sales channels → Develop apps, with the `read_content`, `write_content`, `read_products` and `write_products` scopes). Use this when the one-click OAuth connect is unavailable or when your users prefer not to install a third-party app on their store. The token is validated against the store before anything is saved; custom-app tokens do not expire. Connecting the same profile to a store again replaces the stored token in place.
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.