Update a hub's name, websites, or notes

Renames the hub and/or merges websites and notes into it, then rebuilds it in the background (202). Websites merge by URL — a URL the hub already has is re-crawled, a new one is added — and notes merge by filename, so sending a known filename edits that note in place and keeps its attachment. Nothing is ever removed: there is no public way to drop a website or a note. The hub flips to status processing immediately; the websites and notes in this response are still the PRE-merge values, so poll GET /business/knowledge-hubs/{hubId} until status is complete to see the merged hub. A hub that is already processing a build, update or refresh answers 409 KNOWLEDGE_HUB_NOT_READY.

Errors:

• 404 KNOWLEDGE_HUB_NOT_FOUND — No hub with that id, it was deleted, or it belongs to another team.
• 409 KNOWLEDGE_HUB_NOT_READY — The hub is already processing a build, update or refresh — wait for status complete.
• 422 VALIDATION_FAILED — Nothing to update, a value outside its limits, or a website URL the crawler cannot parse.
• 500 UNEXPECTED_ERROR — The update workflow could not be enqueued; the hub may be left processing — retry.
• 429 RATE_LIMITED — More than 30 knowledge-hub/campaign requests in a minute (or 1000 in a day). Knowledge hubs share the campaigns bucket.

Requires one of the following token scopes: campaigns.