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
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
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
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
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
60-second retry matrix
List public help-center articles
GET /api/v1/public/help/articlesorg 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}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/brandingorg 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/categoriesorg 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/searchorg 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}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/feedbackOpen a public help-center support ticket
POST /api/v1/public/help/tickets