Personal API tokens
Personal API tokens authenticate HQ API and MCP requests as your HQ account. They are separate from the single-website credentials used by the Website Publishing API.
Create a token
Section titled “Create a token”- Sign in to HQ.
- Open Settings → API tokens.
- Create a named token, select its permissions and expiration, and copy it once.
- Store it in your calling tool’s secret settings or server environment.
Available expiration options are 30 days, 90 days, one year or no expiration. The token list shows its prefix, creation, expiration, last use and revocation status. You can revoke your own tokens in Settings.
Permissions
Section titled “Permissions”A token’s selected scopes are a ceiling. On each request, HQ also checks your current role, business access and resource assignments. A later role promotion does not add capabilities to an already-issued scoped token.
Tool discovery shows only the tools available to that credential. Handlers enforce the same permissions when a tool is called. An expired or revoked token is refused even if the request also carries a browser session cookie.
Use the token
Section titled “Use the token”Authorization: Bearer YOUR_HQ_TOKENUse the token with documented HQ /api/ endpoints or
the MCP endpoint at https://seo.pulpsense.com/api/mcp.
Tokens do not authenticate ordinary HQ pages or sign-in URLs. Token management
remains in HQ Settings; API tokens and OAuth connections cannot create, list or
revoke personal tokens.
Replace tokens labelled All current permissions (legacy) in Settings when you want an explicitly scoped permission ceiling.