Skip to main content
PATCH
Correct a learned fact

Authorizations

Authorization
string
header
required

Your API token (af_…) as the Basic-auth username, with an empty password.

Path Parameters

factId
string
required

24-character hex id of the learned fact (from GET /business/knowledge-hubs/learned-facts).

Body

application/json

At least one of claim or category is required.

claim
string

Corrected claim text (1-1000 characters). Free text — there is no vocabulary — but it must stay anonymized: a deterministic gate answers 422 LEARNED_FACT_NOT_ANONYMIZED when the claim contains an email address, a run of 9 or more phone-like digits, a currency amount in the same claim as deal language (discount, quote, contract, renewal, proposal, negotiated, agreed), or contract vocabulary (renewal date, contract term, termination clause, auto-renew, payment terms, net 30/60/90, master service agreement, MSA, SOW, non-disclosure, NDA). Person and customer names are NOT checked, so keep them out yourself. The edit reaches the hub's pages on the next daily learning run, not immediately.

Required string length: 1 - 1000
category
enum<string>

Fact category, one of overview (company summary), products, pricing, icp-use-cases (ideal customers and use cases), differentiators, competitors, faq, source-digest (digest of one source), custom (user-authored), objection (a buyer objection) or faq-insight (a recurring question).

Available options:
overview,
products,
pricing,
icp-use-cases,
differentiators,
competitors,
faq,
source-digest,
custom,
objection,
faq-insight

Response

Success

fact
object
required

The fields the update reports. Read the fact back from the list endpoint for the rest.