Skip to main content

Help Center API

Published help-center articles, categories, full-text search, branding, and visitor support tickets on your hosted portal Base path: /api/v1/public/help Endpoint count: 8

title: “Errors worth branching on” description: “Per-endpoint failure templates matching the envelope — what actually fires, what to retry, what to surface to the operator.”

Errors worth branching on

These five failures cover the article fetch (GET /api/v1/help-center/articles/), on every docs-embed hit from the widget. Each block below is a full { error, meta } envelope as the API returns it, and the matrix at the bottom answers retry vs surface for the same five classes. For the platform-wide decision table these branches plug into, see the error handling guide.

401 — Unauthorized

A 401 on this page is the bearer key failing before the route ran — it never means the resource is wrong. Rotate the key or re-mint the scoped token; retrying the same request changes nothing.

403 — Forbidden

A 403 means the key authenticated but the operation is gated by scope — check the key’s scopes on the developer page; a 403 is never a data-not-found shape.

422 — Schema

A 422 means the payload did not match the request schema — branch on error.details.field and resend with the nearest published slug or the fallback collection landing instead of blind-retrying the same body.

429 — Rate

The Retry-After header and error.details.retry_after are both set on every 429 — resend the SAME request after the lower of the two.

404 — Not found

Surface the human slug suggestion; never retry on a 404.

60-second retry matrix


List public help-center articles

GET /api/v1/public/help/articles
Returns a tenant’s published, public help-center articles for the organization named by the org query parameter. Optionally filter by category and section slug and sort by recent (default) or most-viewed. Each item carries the article slug, title, summary, last-updated time, and view count. Use it to render the help-center article index.

Get a public help-center article

GET /api/v1/public/help/articles/{slug}
Returns a single published, public help-center article by slug for the organization named by the org query parameter, and records a view. The response includes the article title, summary, markdown body, timestamps, and view count. An unknown, unpublished, or private slug returns 404.
string
required
—

Get public help-center branding

GET /api/v1/public/help/branding
Returns the public-safe help-center branding for the organization named by the org query parameter: the logo, primary and secondary colours, header links, and whether the Orbit credit is shown. Unset fields fall back to the platform default theme. The help-center pages read this once on load to apply the tenant’s white-label look.

List public help-center categories

GET /api/v1/public/help/categories
Returns the public help-center taxonomy tree for the organization named by the org query parameter: every public category with its nested public sections and a rolled-up count of visible articles. The help-center navigation reads this to render its “browse by topic” grouping.

Search public help-center articles

GET /api/v1/public/help/search
Full-text search across a tenant’s published, public help-center articles for the organization named by the org query parameter. Pass the search terms in q; title matches rank ahead of body matches. Use it to power the help-center search box so a visitor can self-serve before opening a ticket.

Get public help-center ticket status

GET /api/v1/public/help/tickets/{id}
Returns the status and public reply thread for a help-center ticket the visitor opened, authorised by the capability token from the submission receipt plus the org query parameter. Lets an unauthenticated visitor track a request without a dashboard account; a bad token, unknown org, or unknown ticket all return the same 404.
string
required
—

Submit help-center article feedback

POST /api/v1/public/help/feedback
Records a visitor’s “was this helpful?” vote, with an optional comment, against a published, public help-center article for the organization named in the body. The visitor IP is hashed, never stored raw. Use it to capture article-level helpfulness signals from the public help center.

Open a public help-center support ticket

POST /api/v1/public/help/tickets
Lets an unauthenticated help-center visitor open a support ticket for the organization named in the body, with a subject, message, contact email, and the slugs of any articles they read first. Use it when a visitor cannot self-serve via articles and needs to reach support before signing in.