PilotScribe publishes to WordPress through the built-in REST API, authenticated with an Application Password — a dedicated credential you generate inside WordPress, separate from your login password. You'll collect three values and paste them into the Publishing tab of your site in PilotScribe.

Requirements: WordPress 5.6 or newer, served over HTTPS. Application Passwords are disabled on plain HTTP.

What you'll need

  • REST API endpoint — your site root + /wp-json
  • Username — your WordPress login username
  • Application Password — not your login password

Steps

  1. Find your REST API endpoint. It is your site root followed by /wp-json — for example https://yourblog.com/wp-json. Use the site root, not the homepage URL of a post or page, and do not add anything after /wp-json.
  2. Open your profile. In your WordPress dashboard, go to WP Admin > Users > Profile.
  3. Create an Application Password. Scroll to Application Passwords, type a name (e.g. PilotScribe) and click Add New. WordPress shows the generated password once — copy it now. This is not your login password.
  4. Note your username. It's the username of the account you just created the Application Password for (shown on the same Profile page).
  5. Paste into PilotScribe. In app.pilotscribe.com, open your site, go to the Publishing tab, choose WordPress, then fill in:
    • REST API endpoint → your …/wp-json URL
    • Username → your WordPress username
    • Application Password → the value you just copied
    Run Test connection to verify the credentials, then save.

Scopes & permissions

Application Passwords inherit the role of the user that created them. Use an account whose role can create and publish posts (Author, Editor or Administrator). Keep it minimal: a dedicated Editor-role account is enough and limits what the credential can touch.