Build against your feedback loop.

List every project the API key can see (scoped to a single Hollahoop organisation).

List feedback boards on a project (e.g. feature-requests, bugs, general).

List the post-status workflow for a project (Open / Planned / In progress / Shipped / Declined and any custom ones).

List feedback tags for a project (slug, label, color).

List survey campaigns on a project (NPS / CSAT), including response_count and summary_score.

Get one survey campaign with summary_score, response_count, and recent responses.

List support inbox tickets for a project. Spam is hidden unless status=spam. Most recently active first.

Get one support ticket and its messages (oldest first), scoped to a project.

List feedback posts on a project, optionally filtered by board and/or status. Default sort is by vote count.

Fetch a single post by id, including its comments.

Read the publish guard rules for a project: effective action per category (security, internal, embarrassing, minor, off_topic), plus the org and project overrides. Null project values inherit from the org.

Dry run the publish guard on a title and body without saving anything. Returns the decision (publish, rewrite, hold, skip), the category, the reason, and the text that would be published.

List comments on a feedback post, oldest first. Use limit and offset to paginate; get_post also returns comments inline.

List changelog / Updates entries for a project (drafts and published).

Fetch a single changelog / Updates entry by id or slug.

List documentation pages for a project, grouped by section. Use the `visibility` filter to scope to public or internal pages.

Fetch a single documentation page by id or slug, including Markdown body. When using a slug, scope with locale and version to match list_docs / upsert_doc_page.

Free-text search across posts, changelog entries, and docs for a project. Uses PostgreSQL full-text search (ts_rank) when available, with ILIKE fallback. Semantic pgvector search is on the roadmap.

Read the public status page payload for a project (components + recent incidents). Requires the project status page to be enabled. Useful for embedding status in dashboards.

List email subscribers who opted in on the public status page (newest first). Project members only; unsubscribe tokens are never returned.

List custom hostnames for a project, including TXT challenge values for pending rows.

List Huddle sites (customer websites that collect on-page feedback pins) for a project, with open and resolved pin counts and last activity.

List page and site approvals left from the Huddle overlay ("Approve this page" / "Approve the whole site"), newest first, with who approved and when. state=all includes withdrawn approvals and the reason.

List Huddle feedback pins on a project, newest first. Filter by site_id, page_url, and state (open, resolved, or all; default open).

Fetch one Huddle pin with its page, anchor, linked feedback post, and the comment thread on that post.

Create a new project under this API key’s organisation. Returns the project plus the URL of its public board. Default boards, statuses, changelog tags, and docs section are auto-seeded.

Update an existing project: slug (rename; the old slug keeps working and redirects), name, tagline, description, accent_color, and/or is_public (visibility of the public board). Accepts the project slug or id. Returns the updated project plus its public board URL.

Create a feedback tag on a project.

Delete a feedback tag from a project. Removes the tag from all posts that used it.

Replace the tags on a feedback post (full set). Pass an empty tag_ids array to clear.

Create an NPS or CSAT survey campaign on a project. Returns the campaign id and public response URL.

Update a survey campaign (activate/deactivate and/or edit title/question). At least one field required.

Permanently delete a survey campaign and all of its responses from a project.

Create a support ticket with an opening inbound message. Defaults to status=open, priority=normal.

Update a support ticket status, priority, and/or assignee. At least one field required.

Add a message to a support ticket. Outbound replies move new/pending tickets to open.

Create a new feedback / roadmap post. Defaults to the feature-requests board and the project default status (Open).

Set project-level publish guard rules. on_security / on_internal / on_embarrassing / on_minor / on_off_topic take publish, rewrite, hold, skip, or null to inherit from the org. Owners and admins can always change them; members only while the org lets projects override.

Edit the title and/or body of an existing feedback or roadmap post. The new wording passes the publish guard like create_post. Use update_post_status for status, pin, lock or release estimate.

Update a post: roadmap status, pin/lock flags, and/or release estimate. Status moves accept feedback (open → planned), start work, or ship.

Add a comment (or reply, via parent_id) to a post. The author is the user who created this API key.

Alias of comment_on_post. Add a comment (or reply, via parent_id) to a post. The author is the user who created this API key.

Cast a vote on a post as the API key owner. Idempotent: if the user already voted, returns ok without double-counting. Authors cannot vote on their own posts.

Create a changelog / Updates entry. Set publish=false to leave it as a draft. Auto-derives a slug from the title if none is given. The optional `tag` becomes the pill on the public Updates feed. The optional `translations` ({ "fi": { title, body_md } }) show readers their language; the entry keeps one slug, date and notification.

Edit an existing changelog / Updates entry (title, body_md, tag, translations) and/or publish it with publish=true. `translations` merges per locale: a { title, body_md } value replaces that locale, null removes it, other locales stay. publish=false moves a published entry back to draft. The slug never changes. Publishing runs the same public-safety check as publish_changelog, including all translation text.

Create or update a documentation page (uniquely identified by project + slug + locale). Body is Markdown. Pass visibility=internal to keep the page hidden from the public site.

Remove a status-page email subscriber (same effect as the public unsubscribe link). Pending incident emails for that subscriber are dropped via cascade.

Enable or disable the public status page for a project (same as Settings → Status page).

Open a status-page incident (starts in investigating). Does not require the public status page to be enabled.

Post an update on a status-page incident and advance its lifecycle (investigating → identified → monitoring → resolved).

Add a component to the project status page.

Set the current operational status of a status-page component (for automation / CI hooks).

Record a CI run (GitHub Actions, GitLab CI, or generic) against a project. Same payload as POST /api/integrations/ci/webhook.

Add a custom hostname to a project. Returns the TXT name and value to publish, then call verify_domain. Needs the Starter plan or higher; Free orgs get a plan_required error.

Check the TXT challenge for a pending custom hostname and mark it verified when the record matches. Verifying a pending hostname needs the Starter plan or higher (plan_required otherwise); verified hostnames keep working on any plan.

Register a customer website for Huddle on-page feedback. Detects the platform when not given and returns the install snippet (or WordPress plugin steps). New sites start as draft and review-only; set status live to start collecting pins.

Change a Huddle site: status (draft, live, paused), white label branding (accent, toolbar_bg, toolbar_text, radius, label, display_name, position, logo_url, hide_branding, board; null clears a field), logo_upload (PNG, JPEG or WebP; no SVG), platform, install method, review_only (overlay only for guest links, staff and signed users), unapprove_on_new_pin, extra allowed origins (staging hosts), or the query params that make a different page. Hiding the Hollahoop credit needs the Starter plan or higher. Returns the site, the branding guests will really see (unreadable text colours are replaced) and a fresh install snippet.

Post a staff reply on the thread behind a Huddle pin (a comment on its linked feedback post). The publish guard runs first; held or skipped replies are refused. The author is the user who created this API key.

Mark a Huddle pin as resolved. It disappears from the live site and fires huddle.pin.resolved.

Reopen a resolved Huddle pin so it shows on the live site again. Fires huddle.pin.reopened.

Create a time-limited guest review link for a Huddle site so a client can leave pins without an account. The review_url is shown once; only a hash is stored.

Revoke a Huddle guest review link right away. Revoking twice is a no-op.