Knowledge hubs

A knowledge hub is your company’s ingested content — site pages, docs, product material — that grounds AI campaign generation. When an AI campaign is generated against a hub, the emails reflect your actual product and voice instead of generic copy inferred from a prompt. Hubs are created and populated in the Fuse app; the API’s role is smaller. You list the hubs that exist and pick one at campaign creation. There are no endpoints for creating or ingesting content into a hub.

Listing knowledge hubs requires a key with the campaigns scope. See scopes.

List your knowledge hubs

curl https://api.tryfuse.ai/api/v1/business/knowledge-hubs \
  -u "af_YOUR_KEY:"

{
  "knowledgeHubs": [
    {
      "id": "68a1f8509c41d20014b3ee41",
      "name": "Brightpay KB",
      "companyName": "Brightpay",
      "status": "complete",
      "isDefault": true,
      "createdAt": "2026-06-01T12:00:00.000Z"
    }
  ]
}

Field	Meaning
`id`	The value to pass as `knowledgeHubId` when creating an AI campaign.
`name`	The hub’s name as set in the app.
`companyName`	The company whose content the hub holds.
`status`	`processing` or `complete` — see below.
`isDefault`	The hub used when an AI campaign doesn’t specify one.
`createdAt`	When the hub was created.

A hub with status processing is still ingesting content. You can ground a campaign on it, but generation only draws on what has been ingested so far, so the result is thinner than waiting for complete. If you control the timing, poll until the hub reports complete before creating the campaign.

Use a hub in a campaign

Pass the hub’s id as knowledgeHubId when creating an AI campaign. It only applies to AI-generated campaigns — manual campaigns bring their own copy, so there is nothing for a hub to ground.

curl -X POST https://api.tryfuse.ai/api/v1/business/campaigns \
  -u "af_YOUR_KEY:" \
  -H "Content-Type: application/json" \
  -d '{
    "campaignName": "Q3 outbound - finance leaders",
    "campaignType": "ai-generated",
    "listId": "68a1f20b9c41d20014b3e901",
    "knowledgeHubId": "68a1f8509c41d20014b3ee41"
  }'

If you omit knowledgeHubId, generation uses the hub marked isDefault: true. If you name a hub that doesn’t exist or doesn’t belong to you, the request fails with 404 KNOWLEDGE_HUB_NOT_FOUND in the standard error envelope:

{
  "error": {
    "code": "KNOWLEDGE_HUB_NOT_FOUND",
    "message": "The requested knowledge hub was not found.",
    "param": null,
    "doc_url": "https://docs.fuseai.com/concepts/errors#knowledge_hub_not_found",
    "request_id": "req_8fK2mQ4x"
  }
}

The API never falls back silently to your default when you name a hub explicitly. A campaign grounded on the wrong company’s content is worse than an error, so a bad knowledgeHubId fails loudly instead of quietly producing emails about someone else’s product.

Keep a hub current

A hub is not frozen once it is built. Four things can change after the crawl.

Re-crawl one website

POST /business/knowledge-hubs/{hubId}/refresh takes the url of a site already on the hub and crawls it again. It answers 202; the hub returns to processing while it works.

curl -X POST https://api.tryfuse.ai/api/v1/business/knowledge-hubs/$HUB_ID/refresh \
  -u "$FUSE_API_KEY:" -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com/pricing" }'

The URL must already be one of the hub’s sites — refresh re-reads a source, it does not add one.

Edit a page

Pages are the readable summaries the crawl produced. Edit one with PATCH /business/knowledge-hubs/{hubId}/pages/{pageId} (title, content, or both), remove one with DELETE, or rebuild one from its sources:

curl -X POST https://api.tryfuse.ai/api/v1/business/knowledge-hubs/$HUB_ID/pages/$PAGE_ID/regenerate \
  -u "$FUSE_API_KEY:"

Regenerating discards your edits and rewrites the page from what the hub crawled, so use it when the source changed rather than when the wording is wrong.

A page carries an origin: generated if the crawl wrote it, edited once you have changed it, user if you added it yourself. An edited page is still rebuilt when you regenerate it.

Attach a document to a note

Notes hold context the crawl could not reach. A note can carry one file — a deck, a one-pager, a price list — sent as base64:

curl -X POST https://api.tryfuse.ai/api/v1/business/knowledge-hubs/$HUB_ID/attachments \
  -u "$FUSE_API_KEY:" -H "Content-Type: application/json" \
  -d '{
    "noteId": "68a1f8509c41d20014b3ee55",
    "filename": "positioning.pdf",
    "contentType": "application/pdf",
    "fileBase64": "JVBERi0xLjQK..."
  }'

GET /business/knowledge-hubs/{hubId}/attachments/{noteId} returns a short-lived downloadUrl for it.

DELETE /business/knowledge-hubs/{hubId}/attachments/{noteId} removes the whole note, not just its file — the note’s text goes with it. Re-add the note if you only meant to drop the document.

A note already holding a file answers 409 ATTACHMENT_ALREADY_EXISTS; there is no replace, so delete and re-add.

Correct what Fuse learned

Fuse also learns facts from your team’s own conversations — questions prospects keep asking, objections that keep landing. GET /business/knowledge-hubs/learned-facts lists them across the team:

{
  "facts": [
    {
      "id": "68a1fb0a9c41d20014b3f201",
      "claim": "Prospects frequently ask whether a SOC 2 report is available before a trial.",
      "category": "faq-insight"
    }
  ]
}

A wrong or stale one can be corrected with PATCH /business/knowledge-hubs/learned-facts/{factId} or dropped with DELETE. Corrections must stay anonymised — a claim naming a person or a customer is refused with 422 LEARNED_FACT_NOT_ANONYMIZED.

Where to next

Campaigns

The full campaign creation flow, including the rest of the AI generation options.

API reference

Complete request and response schemas for every endpoint.

Get started

Concepts

Guides

CRM sync

Power dialer

Deep Research

Signals

MCP server

List your knowledge hubs

Use a hub in a campaign

Keep a hub current

Re-crawl one website

Edit a page

Attach a document to a note

Correct what Fuse learned

Where to next

Campaigns

API reference

​List your knowledge hubs

​Use a hub in a campaign

​Keep a hub current

​Re-crawl one website

​Edit a page

​Attach a document to a note

​Correct what Fuse learned

​Where to next

Campaigns

API reference

List your knowledge hubs

Use a hub in a campaign

Keep a hub current

Re-crawl one website

Edit a page

Attach a document to a note

Correct what Fuse learned

Where to next