Skip to main content

Record Decisions

Accept a merge, split a record into single records, or reopen a decision. Decisions are keyed by members, survive re-runs and apply before the call returns.

POST /v1/master-records/{domain}/records/{key}/decision records a person's decision on a record. accept keeps the merge and gives the record status accepted. split breaks it into single records with status split. reopen removes an earlier decision. The decision is keyed by the record's members, so it survives re-runs, and the domain is resolved again at once, so the decision takes effect before the call returns.

The call needs the write scope and a key whose person is a member or above. It returns 201 with the key, the decision and the statistics of the run it triggered. A refused request stores nothing. 404 means an unknown domain, or that neither a record nor a decision has this key; 422 means no sources are configured for the domain, so the re-run cannot happen.

POST/v1/master-records/{domain}/records/{key}/decision

Path and body

domain*stringvendors, customers or materials.
key*stringThe record key from the overview.
decision*stringaccept, split or reopen.

Response fields

keystringThe record key the decision is stored under.
decisionstringThe decision recorded.
statsobjectStatistics of the run the decision triggered, in the shape of the run response.

cURL: Split a wrong merge

curl -X POST "https://api.talonic.com/v1/master-records/vendors/records/3a7f9d1c5e2b8046a1d3c7f09b4e6a28d5c1f390/decision" \
  -H "Authorization: Bearer $TALONIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"decision": "split"}'

Response: 201 Decision and statistics (abridged)

{ "key": "3a7f9d1c5e2b8046a1d3c7f09b4e6a28d5c1f390", "decision": "split", "stats": { "source_rows": 2444, "records": 2109, "multi_source": 300, "to_review": 38 } }
After a split, the members are single records and the old key no longer names a record. To undo the split, send reopen with the same key: a decision can be removed even when no record has that key any more. An accepted merge whose membership later changes is a different record with a different key, and the old decision does not carry over.

Frequently asked questions

Does a decision survive the next run?+
Yes. The decision is keyed by the sorted members of the record and a run applies it. If the membership changes, for example because a new row joins the cluster, the record gets a new key and the old decision does not apply to it.
Why does the call take as long as a run?+
The domain is resolved again at once, so the decision takes effect before the call returns. The statistics in the response are those of that run.
How do I undo a decision?+
Send reopen with the same key. It deletes the stored decision and the domain is resolved again, so the record returns to the status the resolution gives it.

Related

Master Records Overview
Golden Records
Run a Domain
Crosswalk