Bring a boundary group (boundary:journal|<code> or boundary:account|<code>) back inside the Scope 3 boundary. The reviewer's decision joins the upload's boundary policy and the organization's memory (source reviewer, above every other), and a regroup job moves the group's rows to the keys the policy now gives them, deciding and matching only the groups that are new; every row and cent of the ledger stays. The group key is percent-encoded as one path segment.
Path parameters
Request body
Response
The regroup job, queued. Poll GET .../factor-agent/jobs/{documentJobId} (kind regroup) until it ends; while it runs the analysis reads processing and names it (jobId). Its progress phases, in order: regroup_classify "Deciding the new keys", regroup_apply "Moving the rows", regroup_match "Matching emission factors", regroup_duplicates "Checking duplicate spend lines", regroup_finish "Finishing the review" (done and total count the rows the regroup moves). A regroup cannot be cancelled.
Changes
Changed in 1 of the 8 revisions of this API.1
- ○
endpoint added
endpoint-added
- ○