Write findings for an exception's lines
Changed onUpserts one finding per record of the exception — the note, status and suggested action your reviewers see on each open line. Findings are keyed on (exception, record), so sending the same record again replaces its finding. Up to 1,000 findings per request; each is validated independently and the response lists the rejected ones, so a partial batch still writes. Records already matched by rules do not need findings — write them for the lines that are left.
Request
- Base URLhttps://api.endclose.com/v1
- AuthAPI key in header X-API-KEY
Path parameters
Headers
Optional. Send the same key when retrying a write you are not sure landed: the first response is returned again (with Idempotent-Replayed: true) instead of writing twice. A key used for a different request is refused with 422; one whose first request is still running gets 409. A refused or failed request does not use up its key. Keys are per environment and kept for 7 days.
Request body
Response
Findings written (possibly with per-finding errors)
Changes
- info
added the new optional
headerrequest parameterIdempotency-Key
- info
- info
endpoint added
- info