SPsponsorunited
News

Correct what the extractor read, or which contact the row points at

Only the fields present in the body are written; an explicit null clears a nullable one. The extractor's confidence, the resolver's score and shortlist, and every field the add pipeline owns are refused rather than ignored, so a caller is never told a write landed when it did not.

patch/api/news/submissions/{id}/contacts/{newsContactId}

Request

Path parameters

idinteger required
newsContactIdinteger required

Request body

namestring

The person's name. Decides which extracted quote attaches when the contact is added, so correcting a mis-read name also fixes quote attachment.

titlestring nullable

Send null to clear it; omit to leave it unchanged.

companystring nullable
role_contextstring nullable

Free text explaining how the person appears in the article.

submitted_linkedin_urlstring nullable

A LinkedIn member profile URL. Distinct from the profile the sourcing agent finds.

matched_contact_idinteger nullable

Point the row at a different platform contact, or send null to clear the match. The person profile and entity columns are derived from it, never sent.

match_status'dismissed' | 'needs_review'

needs_review brings back a row dismissed by mistake.

Example request

{
  "name": "Casey Wasserman",
  "submitted_linkedin_url": "https://www.linkedin.com/in/casey-wasserman/",
  "matched_contact_id": 1377270
}

Response

The contact as it now stands.

Changes

No recorded changes to this operation across all 2 revisions of this API.