fleet

POST /v1/fleet/phish-watch

The box's upload watch graded freshly written site files as suspicious.

All fleet endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

This endpoint does not take an API key. It takes its own credential, issued to the plugin or service that calls it, as a bearer token; see the description above.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/fleet/phish-watch \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "findings": <WorkerPhishWatchFinding[]> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

A worker box's on-box upload watch (docs/1093 §8) scores a site's document root with the phishing detector the moment files in it are written, and the agent posts every MEDIUM/HIGH grade here. A trigger, never a verdict: the engine starts its own scan of THIS box's sites at the reported document roots and acts only on that scan, exactly as the hourly sweep would. Unknown document roots and other boxes' sites are ignored. Answers at once (202); one scan per box and document-root set per two minutes.

Request body

NameTypeRequiredWhat it is
findingsWorkerPhishWatchFinding[]Yes—

Response

NameTypeRequiredWhat it is
acceptedintegerYes—
workflow_idstringYes—

Errors this endpoint can return

401 · 422 · 429