OpenapiHelp
Returns one public article by slug, with its body.
Returns one public article by slug, with its body.
GET /v1/help/articles/{slug}
| Address | https://api.hanzo.ai/v1/help/articles/{slug} |
| Method | GET |
| Operation | get_help_articles_by_slug |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns one public article by slug, with its body. A missing, Draft, or internal (non-public) article is 404 — fail-closed, so this route is no existence oracle for anything beyond "published and public".
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
slug | path | string | yes | Slug is the article's public identifier, from the path. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | helpArticle | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
body | body | string | — | Body is the article's rich-text content as the author saved it. |
category | body | string | — | Category is the name of the knowledge-base section the article sits in, or empty when it is filed under none. |
excerpt | body | string | — | Excerpt is the short summary the author wrote for listings, or empty. |
slug | body | string | — | Slug is the article's stable public identifier — the path segment it was addressed by. |
title | body | string | — | Title is the article's headline. |
updatedAt | body | integer | — | UpdatedAt is the unix second the article was last written. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, HelpApi } from 'hanzoai';
const api = new HelpApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getHelpArticlesBySlug({ slug: 'slug' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import HelpApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = HelpApi(client).get_help_articles_by_slug(slug='slug')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.HelpAPI.GetHelpArticlesBySlug(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, help_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = help_api::get_help_articles_by_slug(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.HelpApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new HelpApi(client).getHelpArticlesBySlug();curl https://api.hanzo.ai/v1/help/articles/<slug> \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches help through the help tool, which names its 4 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_help_articles"
}
}
}'How is this guide?