Integration
Connect PhishStats to Easybill
When something happens in PhishStats, your agent does the next thing in Easybill. 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 Easybill 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 Easybill
Triggers and actions 1 trigger · 15 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.
- Find phishing records
Search 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 customerCreate a new customer. POST /customers
- Add document
Create a new document (invoice, quote, etc). POST /documents
- Add project
Create a new project. POST /projects
- Add task
Create a new task. POST /tasks
- Add time tracking
Create a new time tracking entry. POST /time-trackings
- Delete customer
Delete a customer. DELETE /customers/{id}
- Delete document
Delete a document. DELETE /documents/{id}
- Get customer
Fetch a single customer by id. GET /customers/{id}
- Get document
Fetch a single document by id. GET /documents/{id}
- List documents
Fetch a list of documents. GET /documents
- List projects
Fetch a list of projects. GET /projects
- List tasks
Fetch a list of tasks. GET /tasks
- Update customer
Update an existing customer. PUT /customers/{id}
- Update document
Update an existing document. PUT /documents/{id}
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