Integration
Connect PhishStats to Pushover
When something happens in PhishStats, your agent does the next thing in Pushover. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want PhishStats and Pushover to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with PhishStats and Pushover
Triggers and actions 1 trigger · 10 actions
Trigger
New phishing recordPolling trigger for newly added phishing URLs. GET https://api.phishstats.info/api/phishing?_sort=-date&_p=1&_size=100 (optionally filtered by _where=(countrycode|tld|asn,eq,value) etc.) — the database refreshes every ~90 minutes; poll no more often than that. Dedup/order by the id or date field (descending). Auth via X-API-Key header (psk_...) or ?apikey=psk_...; anonymous allowed at a lower quota.
Action
Find phishing recordsSearch the PhishStats phishing database. GET https://api.phishstats.info/api/phishing with _where=(field,operator,value) filters (eq/ne/gt/lt/like, combined with ~and/~or) over fields like url, ip, asn, countrycode, tld, title, score, date, id; _sort=field (-field for desc); _p=page (default 1), _size=records per page (default 20, max 100). Auth via X-API-Key header (psk_...), Authorization: Bearer psk_..., or ?apikey=psk_... query param; anonymous is allowed at a lower quota.
Action
Add GroupCreate a new Pushover delivery group. POST https://api.pushover.net/1/groups.json with token + name.
Action
Cancel Emergency Retry by ReceiptStop the ongoing retries of an emergency-priority notification by its receipt before it is acknowledged.
Action
Cancel Emergency Retry by TagStop the ongoing retries of all emergency-priority notifications sharing a given tag before they are acknowledged.
Action
Check ReceiptCheck the acknowledgement status of an emergency-priority (priority 2) notification by its receipt.
Action
Get GroupRetrieve a delivery group's info + member users. GET https://api.pushover.net/1/groups/{group_key}.json?token=...
Action
List SoundsRetrieve the list of notification sounds available to Pushover devices.
Action
Send NotificationSend a push notification to your Pushover devices with optional title, priority, sound, URL, and attachment.
Action
Update GroupRename a delivery group. POST https://api.pushover.net/1/groups/{group_key}/rename.json with token + name.
Action
Validate UserVerify that a Pushover user or group key is valid and has at least one active device.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews