Skip to content

Website API authentication

Every Website Publishing request uses a bearer token issued by PulpSense for one managed website. The token begins with wp_ and is returned once when issued.

Authorization: Bearer YOUR_WEBSITE_TOKEN

The website is determined from this credential. Requests cannot select a different website using a query parameter or request body.

Scope Operations
read Read pages, articles, histories and jobs
edit Create and update supported content, upload media and request previews
publish Publish content to the launched website; editing permission is also required

Production publication requires the managed website’s initial launch to have completed. Requesting a production publication before launch returns 409.

Keep the token in the calling tool’s secret settings or server environment. Send it in the Authorization header. Requests with a different browser Origin are refused with 403; this API is intended for server-to-server use.

Website endpoints accept website tokens. General HQ tokens, browser session cookies and internal service credentials are not substitutes.

Your token has an expiration set when it is issued, within one year. PulpSense can revoke it earlier or issue a replacement. Invalid, expired and revoked credentials return 401. Ask PulpSense to replace the credential when needed.

Authenticated JSON responses use Cache-Control: private, no-store.