Developers /Monitoring API

Submit change feedback

Say whether a change mattered; "not_relevant" ones teach the watch's intent.

POST/crawl/v1/monitors/{monitor_id}/changes/{result_id}/feedback
POST example
curl --request POST \
  --url 'https://factget.dev/crawl/v1/monitors/{monitor_id}/changes/{result_id}/feedback' \
  --header "Authorization: Bearer $FACTGET_CRAWL_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "verdict": "relevant"
}'

Replace IDs and sample values with your own. Examples are not executed in your browser.

Authorization

Authorizationstring · header · required

Bearer Crawl API key with the required scope. Learn about authentication →

Parameters

Path parameters

monitor_idstringrequired
result_idintegerrequired
minimum: 1

Request body

application/json
verdictstringrequired
Allowed: "relevant", "not_relevant"

Responses

200Successful Response
application/json

The published schema does not define individual response fields for this endpoint. Inspect the returned JSON in your integration.

422Validation Error
application/json
detailobject[]
Show item properties
locstring | integer[]required
msgstringrequired
typestringrequired
inputobject
ctxobject

The API schema lists the responses above. Long-running operations can also return 202; see async jobs. For application errors, see errors & retries.