Update a corroboration
update_corroborationIdempotent
Update the sheet of a corroboration: only the fields you send change (an empty label goes back to the derived one, an empty notes or published_on clears it). Correcting the url ALWAYS recomputes the source: the two never drift apart. It also carries monitoring, the cadence at which the page is read again on its own, which is why watching a page needs no tool of its own. To say a page is gone, use archive_corroboration instead: editing never takes anything down.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Absolute http(s) address of the EXACT page where the third party talks about the brand, never the home page of the site. | |
| label | No | Display name of the page. OMIT IT: it is derived from the address (domain and path). Send an empty string to go back to the derived one. | |
| notes | No | Free notes: the passage that mentions the brand, the contact, how the page came about. | |
| monitoring | No | How often the page is read again on its own: "off" (the default), "daily", "weekly" or "monthly". Each executed check costs 0.02 USD from the prepaid balance and returns the same two findings as verify_corroboration, on the mention and on the link, plus an email when the text of the passage changed or the link is gone. It states a STATE, so sending the same value again does nothing. It applies to a live line whose page reads (readability "html"): elsewhere the reply is 409 corroboration_archived or 409 page_not_readable, and "off" is always accepted. | |
| published_on | No | The day the page was PUBLISHED, as YYYY-MM-DD. Distinct from the recording day, and the one that means something against the citation curves. Omit it when unknown: it is never guessed. | |
| request_channel | No | Whether someone can be asked to change the page: "available" (a contact or a process exists), "none" (nobody to ask), "unknown" (not filled in, the default). It gates the refresh suggestions of the quest file; the contact itself belongs in the notes. | |
| corroboration_id | Yes | The UUID of the corroboration: call list_corroborations to find it. |