In this section

Resources / Developers / GraphQL

GraphQL: account and posts

client_getCurrentAccount and the client post queries, fields and enums.

These operations bootstrap the widget and fetch published posts. All of them take the project key as described in the GraphQL overview.

client_getCurrentAccount

Returns public information about the account that owns the key. It is the first call the embed makes, it applies the plan visitor gate and it counts the browser session as a visitor (once per session).

query {
  client_getCurrentAccount {
    name
    origin
    description
    usageAllowed
    appearance {
      widget
      category
      nps
    }
  }
}
FieldTypeDescription
nameString!Account name.
originString!Registered origin of your site.
descriptionStringOptional account description.
appearanceAppearance!JSON blobs for account defaults: widget, category, nps, survey and roadmap.
usageAllowedBoolean!False when the plan visitor limit is exhausted. See usageAllowed.

client_getAllPosts

query {
  client_getAllPosts(filters: { state: published }) {
    id
    title
    description
    url
    variant
    category
    channels
    flags
    state
    appearance
    mainLanguage
    translations
    startDate
    endDate
  }
}

Optional appearance on a post is an override over account appearance.widget / category colors. When missing or { useCustom: false }, the embed uses account defaults. Surveys and roadmaps follow the same inherit pattern with appearance.survey and appearance.roadmap.

mainLanguage and translations (JSON map of locale → sparse string overlays) drive visitor-facing localization in the embed. Empty overlay fields fall back to the main-language title/description. NPS, surveys, roadmap and status payloads expose the same pattern. Product guide: Translations and languages.

The client query always returns published posts, whatever you pass in filters.state. It also takes part in the visitor gate: when your allowance is exhausted (usageAllowed is false) it returns an empty list. Use client_getPost(id: ID!) to fetch a single post.

Post enums and category

Field / enumValues
NotificationVarianttopbar, popup, toast, tooltip
category (String)Built-in slugs: message, warning, news, fix, improvement, announcement, feature. Custom slugs: ^[a-z][a-z0-9_-]{0,31}$ (created in the admin app; colors live in account appearance.category).
PostStatepublished, draft, archived, expired
PostFlagcomments, reactions, social_sharing, pinned, preserve
PostChannelwidget, page, push, email

Custom categories

Custom categories are managed under Changelog → Appearance (updateAccount writes colors into appearance.category). deleteCustomPostCategory(slug) removes a custom key and sets matching posts’ category to "" (the admin/widget UI shows Post for an empty category — that label is not a stored value). Built-in slugs cannot be deleted. At most 20 custom keys. GraphQL category is a String.

push and email are not delivered

The PostChannel enum contains push and email, but Hubbo does not deliver posts by push or email. Only widget and page produce anything visitors can see. Do not build on the other two values.

Live updates

There are no public client_* subscriptions for accounts or posts. The widget and public changelog page load content with queries; admin edits appear on the next load or refetch. Guest chat on a public changelog page is the exception — see Realtime subscriptions.

Changelog page

Changelog can be read as web pages at https://app.hubbo.io/page/{key}. See Public URLs.