OpenAPI and Swagger
Every endpoint is schema-defined and documented, and can be tried live from the browser with your token.
PLATFORM REST API, scoped keys, teams and notifications
Every module is exposed through a REST API with an OpenAPI schema. Scoped keys, team-based permissions and notification rules fit the platform to how your organisation works.
Screenshots are taken from a demo tenant; organisation names and data are entirely fictional.
A threat intelligence platform that stays an island does not get used. InsightGuard's API serves the same data as the interface: cases, IoC lists, the IP feed and hunting rules. Keys are issued with only the permissions they need, teams see their own modules, and critical-finding notifications reach the right person.
What it does
Every endpoint is schema-defined and documented, and can be tried live from the browser with your token.
Permissions such as cases:read or ioc_lists:write are chosen one by one; keys expire and are shown only once.
Teams such as SOC, brand protection or attack surface work with their own permission sets; the admin role is separate.
How it works
In Access Control you choose permissions and an expiry, then issue a key.
Your SIEM, SOAR or own script connects with a bearer token and a company ID header.
IoC lists, cases and rules are pulled on a schedule; notifications reach the team on critical events.
Sub-modules
API
Endpoints for token status and scopes, hunting rules, IoC lists and IP feed lists; authentication with a bearer token and …
ACCESS
Issue keys for SIEM integrations and automation: name, expiry and permissions chosen one by one. The key is shown only …
TEAMS
Group users into teams and give each team a shared permission set. Company admin and member roles are separate; the …
NOTIFY
A notification lands when a critical finding is confirmed, a subdomain is taken over, a new phishing domain or underground …
What you get
Next step
In a 30-minute session we run a live scan against your own domains.