Fusion Help Api

Fusion Help API

Use when a developer or admin needs to interact directly with the Fusion Help REST API — reading help content, building custom tooling, or automating content management.

When to use

• Display help articles, FAQs, or release notes inside a Fusion app
• Build custom CLI or automation to manage help content
• Programmatically create, update, or delete help documentation
• Search or suggest help content from an application
• Understand Help API endpoints, authentication, or data models
• Read help content for another system

When not to use

• Using fhelp CLI to sync markdown docs → use fusion-help-docs
• Modifying Fusion.Services.Help backend service code
• General REST API questions unrelated to Help

Required inputs

Instructions

1. Discover the Help API base URL

Resolve URL dynamically or use known patterns:

Dynamic discovery (recommended for production tooling):

GET https://discovery.fusion.equinor.com/service-registry/environments/{env}/services

Look for the service with key: "help" in the response. Use the uri field as the base URL.

2. Authentication

All endpoints require a valid Azure AD bearer token. Token audiences and code samples for frontend, backend, and CLI are in references/authentication.md [blocked].

Quick reference — token audiences:

3. Authorization levels

4. Call the API

Endpoints are versioned — include ?api-version=1.0. Resources: Articles, FAQs, Release Notes, Assets, Search/Suggest, Changelog.

For full CRUD details, request/response bodies, OData filters, and validation rules see references/api-endpoints.md [blocked].

For compact endpoint matrix and OData cheat sheet see references/api-quick-reference.md [blocked].

For response model schemas see references/response-models.md [blocked].

5. Integration patterns

Ready-to-use code samples (React component, release notes banner, FAQ search, C# backend automation, Python scripting) are in references/integration-patterns.md [blocked].

Expected output

• Working code to authenticate and call the Help API
• Correct endpoint URLs and query parameters for the use case
• Understanding of response models and OData query options
• For admin use cases: correct request bodies for create/update/delete
• For integration patterns: sample code in the relevant language/framework

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 — slugs cannot be reused
• sourceSystem tracks which tool created a record — mixing source systems for the same slug causes fhelp CLI to refuse updates (unless --no-validation is used)
• Always test against ci before targeting fprd
• Never hardcode bearer tokens — use DefaultAzureCredential or equivalent
• Image uploads must be PNG; API processes them into WebP for serving