Skip to main content
Infrawatch revisits the internet every day and keeps every observation connected. This page takes you from nothing to a saved investigation and a working API call.

Look something up

Start in the platform. No setup, no API key.

Build an integration

Create a key and make a request.

Watch your own surface

Inventory what you own and work the findings.

Search the internet

1

Open the platform

Sign in at app.infrawatch.com. The dashboard opens on a search box.
2

Ask in plain language

Type what you are looking for, such as Find me all Fortinet devices, and Infrawatch turns it into a query. You do not need to know the syntax yet.
3

Read the result

Every result is an observation with a date attached. Open a host to see its services, DNS history, fingerprints, tags, and any reporting that mentions it.
4

Follow the evidence

Choose Investigate on a host to hand it to InfrAI. It pivots across passive DNS, services, and host inventory at once, then builds a graph you can replay and keep in a project.

Write the query yourself

Once you know what you are looking for, InfraQL is faster than describing it. The basic clause is field:value, and clauses combine with AND, OR, and NOT:
Use same_service(...) when several conditions must hold on the same service rather than anywhere on the host:

Learn InfraQL

Operators, time windows, correlation, and pattern matching.

Make your first API request

1

Create an API key

Open API access, create a key with the search.view scope, and copy its secret.
Store the secret when it is shown. Treat it like a password and never place it in browser code or a public repository.
2

Store it

Every public endpoint lives under https://api.infrawatch.com/api/v1 and authenticates with the X-API-Key header.
3

Search for a host

4

Read the response

A host response contains a hosts array and a pagination object:
The exact observation changes over time. Build against the documented shape rather than the example values.

Choose your next query

Before you go to production

  • Validate generated or user-supplied InfraQL with POST /search/{dataset}/validate before scheduling it.
  • Ignore unknown response fields so backward-compatible additions do not break your client.
  • Set a request timeout and propagate cancellation.
  • Honor 429 and 503 responses with bounded backoff.
  • Log the error request_id; support can use it to trace the request.

Follow an IP investigation

Build host context, inspect services, pivot through DNS, and find reporting.

Browse the field reference

Every searchable field, its type, and the operators it accepts.