Integration

Connect PhishStats to Basin

When something happens in PhishStats, your agent does the next thing in Basin. Describe it in plain language and the automation is built, tested on every branch and kept running.

PhishStats1 triggerPhishStats1 actionBasin1 triggerBasin11 actions

Browse all apps

Build it

What do you want PhishStats and Basin 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 Code

Everything your agent can do with PhishStats and Basin

Triggers and actions 2 triggers · 12 actions

Trigger
New phishing record
Polling 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 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.
Trigger
New Submission
Triggers when your form receives a submission.
Action
Add form
Create a new form under a project. POST /api/v1/forms.
Action
Add project
Create a new project (form-organizing container). POST /api/v1/projects.
Action
Delete form
Destroy a form. DELETE /api/v1/forms/:id.
Action
Delete submission
Destroy a submission. DELETE /api/v1/submissions/:id.
Action
Get form
Retrieve a single form by id. GET /api/v1/forms/:id.
Action
Get submission
Retrieve a single submission by id. GET /api/v1/submissions/:id.
Action
List forms
List all forms accessible to the account. GET /api/v1/forms.
Action
List projects
List all projects accessible to the account. GET /api/v1/projects.
Action
List submissions
List submissions for a form. GET /api/v1/submissions.
Action
Update form
Update a form's configuration (notifications, spam protection, branding, etc). PATCH/PUT /api/v1/forms/:id.
Action
Update submission
Update a submission's state fields (spam, read, trash). PATCH/PUT /api/v1/submissions/:id.

Each app on its own

The other way round: Basin to PhishStats