fusion-help-api
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseFusion Help API
Fusion Help API
Use this skill when a developer or admin needs to interact directly with the Fusion Help REST API — whether to read help content in their own app, build custom tooling, or automate content management.
当开发者或管理员需要直接与Fusion Help REST API交互时,可使用本skill——无论是在自己的应用中读取帮助内容、构建自定义工具,还是自动化内容管理。
When to use
适用场景
- App developer wants to display help articles, FAQs, or release notes inside their Fusion app
- Developer building a custom CLI or automation script to manage help content
- Admin wants to programmatically create, update, or delete help documentation
- Developer needs to search or suggest help content from their application
- Someone wants to understand the Help API endpoints, authentication, or data models
- Building an integration that reads help content for another system
- 应用开发者希望在其Fusion应用内展示帮助文章、常见问题(FAQ)或发布说明
- 开发者构建自定义CLI或自动化脚本以管理帮助内容
- 管理员希望以编程方式创建、更新或删除帮助文档
- 开发者需要从其应用中搜索或推荐帮助内容
- 想要了解Help API的端点、认证方式或数据模型的用户
- 构建集成以向其他系统读取帮助内容的场景
When not to use
不适用场景
- Using the CLI tool to sync markdown docs (use the
fhelpskill instead)fusion-help-docs - Modifying the Fusion.Services.Help backend service code
- General REST API questions unrelated to Help
- 使用CLI工具同步Markdown文档(请改用
fhelpskill)fusion-help-docs - 修改Fusion.Services.Help后端服务代码
- 与Help无关的通用REST API问题
Required inputs
必填输入项
| Input | Required | Description |
|---|---|---|
| Use case | Yes | Reading content, managing content, or searching |
| App key | For scoped queries | The Fusion app key to read/manage help for |
| Target environment | Yes | |
| Auth context | Yes | User token (interactive) or service principal (automation) |
| 输入项 | 是否必填 | 描述 |
|---|---|---|
| 使用场景 | 是 | 读取内容、管理内容或搜索 |
| 应用密钥 | 范围查询时需要 | 用于读取/管理对应Fusion应用的帮助内容的密钥 |
| 目标环境 | 是 | |
| 认证上下文 | 是 | 用户令牌(交互式)或服务主体(自动化) |
Instructions
操作步骤
1. Discover the Help API base URL
1. 查找Help API的基础URL
The Help API is registered in the Fusion service discovery. Resolve the URL dynamically or use the known patterns:
| Environment | Base URL |
|---|---|
| |
| |
| |
Dynamic discovery (recommended for production tooling):
GET https://discovery.fusion.equinor.com/service-registry/environments/{env}/servicesLook for the service with in the response. Use the field as the base URL.
key: "help"uriHelp API已在Fusion服务发现中注册。可动态解析URL,或使用已知的固定格式:
| 环境 | 基础URL |
|---|---|
| |
| |
| |
动态发现(生产工具推荐使用):
GET https://discovery.fusion.equinor.com/service-registry/environments/{env}/services在响应中查找的服务,使用其字段作为基础URL。
key: "help"uri2. Authentication
2. 认证
All endpoints require a valid Azure AD bearer token. Token audiences and code samples for frontend, backend, and CLI are in references/authentication.md.
Quick reference — token audiences:
| Environment | Resource ID (audience) |
|---|---|
| |
| |
所有端点都需要有效的Azure AD承载令牌。前端、后端和CLI的令牌受众及代码示例请查看references/authentication.md。
快速参考——令牌受众:
| 环境 | 资源ID(受众) |
|---|---|
| |
| |
3. Authorization levels
3. 授权级别
| Action | Who can do it |
|---|---|
| Read articles, FAQs, release notes, search | Any authenticated Fusion user |
| Create / Update / Delete articles, FAQs, release notes | App admin, trusted app, or |
| Upload assets (images) | App admin, trusted app, or |
| View changelog (global) | |
| View changelog (per app) | App admin or |
| 操作 | 允许执行者 |
|---|---|
| 读取文章、FAQ、发布说明、搜索 | 任何已认证的Fusion用户 |
| 创建/更新/删除文章、FAQ、发布说明 | 应用管理员、受信任应用或拥有 |
| 上传资源(图片) | 应用管理员、受信任应用或拥有 |
| 查看变更日志(全局) | 仅拥有 |
| 查看变更日志(按应用) | 应用管理员或拥有 |
4. Call the API
4. 调用API
Endpoints are versioned — include in requests. Resources: Articles, FAQs, Release Notes, Assets, Search/Suggest, Changelog.
?api-version=1.0For full CRUD details, request/response bodies, OData filters, and validation rules see references/api-endpoints.md.
For a compact endpoint matrix and OData cheat sheet see references/api-quick-reference.md.
For detailed response model schemas see references/response-models.md.
端点采用版本化管理——请求中需包含。资源包括:Articles、FAQs、Release Notes、Assets、Search/Suggest、Changelog。
?api-version=1.0完整的CRUD详情、请求/响应体、OData筛选器和验证规则请查看references/api-endpoints.md。
如需紧凑的端点矩阵和OData速查表,请查看references/api-quick-reference.md。
如需详细的响应模型架构,请查看references/response-models.md。
5. Integration patterns
5. 集成模式
Ready-to-use code samples for common scenarios (React component, release notes banner, FAQ search, C# backend automation, Python scripting) are in references/integration-patterns.md.
常见场景的即用型代码示例(React组件、发布说明横幅、FAQ搜索、C#后端自动化、Python脚本)请查看references/integration-patterns.md。
Expected output
预期输出
When this skill completes, the user should have:
- Working code to authenticate and call the Help API
- Correct endpoint URLs and query parameters for their use case
- Understanding of the response models and OData query options
- For admin use cases: correct request bodies for create/update/delete operations
- For integration patterns: sample code in the relevant language/framework
当本skill完成后,用户应获得:
- 用于认证并调用Help API的可运行代码
- 符合其使用场景的正确端点URL和查询参数
- 对响应模型和OData查询选项的理解
- 针对管理员场景:用于创建/更新/删除操作的正确请求体
- 针对集成模式:对应语言/框架的示例代码
Safety & constraints
安全与限制
- Read-only endpoints are safe for any authenticated user — no admin permissions needed
- Write operations require app admin, trusted application, or
Fusion.Help.FullControl - Deleted articles/FAQs/release notes are soft-deleted — their slugs cannot be reused
- The field tracks which tool created a record — mixing source systems for the same slug will cause the
sourceSystemCLI to refuse updates (unlessfhelpis used)--no-validation - Always test against environment before targeting
ci(production)fprd - Do not hardcode bearer tokens — always use or equivalent token providers
DefaultAzureCredential - Image uploads must be PNG format; the API processes them into WebP for serving
- 只读端点对任何已认证用户安全可用——无需管理员权限
- 写入操作需要应用管理员、受信任应用或权限
Fusion.Help.FullControl - 删除的文章/FAQ/发布说明为软删除——其slug无法重复使用
- 字段记录创建记录的工具——同一slug混合使用不同源系统会导致
sourceSystemCLI拒绝更新(除非使用fhelp参数)--no-validation - 针对(生产环境)操作前,务必先在
fprd环境测试ci - 请勿硬编码承载令牌——请始终使用或等效的令牌提供程序
DefaultAzureCredential - 图片上传必须为PNG格式;API会将其处理为WebP格式后提供