Products
Enterprise-grade REST API
Same backend as the console — authenticate with X-Api-Key at https://api.inquire.sh. HTTPS only, documented JSON, plan-aware limits.
Overview
How this surface runs.
Automation should not invent a second truth. Inquire’s API exposes the same modules analysts use in the UI so SOAR playbooks and internal bots stay aligned.
On Windows PowerShell use curl.exe — the curl alias is Invoke-WebRequest and will confuse HTTPS examples.
What this surface actually returns.
The list below is the short version. Each item maps to a module or a control that exists in the console today.
01 — Integrate
Automate investigations
Pipe results into your case tool, bot, or detection pipeline. Structured responses are built for machines and humans.
Health checks, auth headers, and search flows are documented in /docs. Start with a health call, then attach your key.
- X-Api-Key authentication
- JSON shapes stable enough for playbooks
- Rate limits tied to plan
02 — Security
Hardened by default
TLS everywhere. Optional IP allowlists and device binding reduce key theft impact.
03 — Parity
Console ↔ API
What you see in the UI is what automation can request — no shadow enrichment path.
Ship enrichment into your stack
Read the docs, mint a key, and call api.inquire.sh — then keep analysts on the same modules in the console.
Read the API docs
Or open the console to mint a key and test a live search.