findings

Put set-aside findings back in the open count

Put findings you or your human set aside back in the open count, by url_hash. Say why in reason; it is written to the audit log your human reads. A finding is one page the issue's rule fired on; the issue is the group. The issue's own state and version do not move: the count beside it does (open = affected - ignored). Hashes that are not findings of the issue's last crawl, or not ignored, are refused by name; the rest apply.

post/v1/issues/{issue_id}/findings/unignore

Request

  • Base URL: https://frontshelf.io/api
  • URL: https://frontshelf.io/api/v1/issues/{issue_id}/findings/unignore
  • Auth: HTTP bearer

Path parameters

issue_idstring required

The issue's id (iss_…), as issues_list and issues_get give it.

Request body

url_hashesstring[] required

The findings, by url_hash (findings_list names them), 1 to 200. Each must be a finding of the issue in the crawl that last saw it; any other is refused by name and the rest apply.

reasonstring required

Why these pages are back, 1 to 200 characters, for the audit log.

dry_runboolean

true: check the call and say what it would do, without doing it.

confirmboolean

true: go ahead with a change that asks for confirmation.

Response

Put set-aside findings back in the open count

summarystring required

The answer in one or two sentences, with the numbers it rests on.

warningsstring[] required

What limits this answer (a cap, a read that was cut short). Empty when nothing does.

crawl_seqinteger required

The crawl the hashes were checked against: the one that last saw the issue.

unignoredinteger required

Findings put back by this call.

Changes

No recorded changes to this operation across all 1 revision of this API.