# PulpSense developer documentation > API references and integration guides for PulpSense. Website Publishing v1 uses a single-website bearer credential. HQ MCP and HQ APIs use personal tokens or supported hosted OAuth with the user's current permissions. ## Website Publishing API - [Quickstart](https://docs.pulpsense.com/website-publishing/quickstart/): List pages, save a revision and request a verified preview. - [Authentication](https://docs.pulpsense.com/website-publishing/authentication/): Website credentials and read/edit/publish scopes. - [Pages](https://docs.pulpsense.com/website-publishing/pages/): Page endpoints, safe structured prose and revision history. - [FAQs and medical schema](https://docs.pulpsense.com/website-publishing/schema/): Visible FAQs and supported structured data fields. - [Articles](https://docs.pulpsense.com/website-publishing/articles/): Manual/imported article creation, edits and publication. - [Images](https://docs.pulpsense.com/website-publishing/media/): Website-owned PNG, JPEG and WebP uploads. - [Preview and publish](https://docs.pulpsense.com/website-publishing/publishing/): Exact-revision jobs, verified URLs and production readiness. - [Errors and retries](https://docs.pulpsense.com/website-publishing/errors/): HTTP errors, revision conflicts and operation identities. ## HQ integrations - [MCP connection](https://docs.pulpsense.com/hq/mcp/): Authenticated HQ tools for MCP-compatible clients. - [Personal tokens](https://docs.pulpsense.com/hq/tokens/): Create, scope, use and revoke your own HQ credentials. - [API changes](https://docs.pulpsense.com/changelog/): Capabilities and compatibility notes.