Wireview API

Domain & IP reconnaissance platform. Solo, no 3rd-party paid APIs. Free tier 50/day.

Base URL https://api.codecaptives.com

Public lookups need no credentials. Everything else needs Authorization: Bearer <jwt>, or X-API-Key for the bulk endpoints. Paste a key below and it is kept in this browser tab only — never sent anywhere but this origin.

Requests go to the host serving this page. From production that is the same origin, so nothing is cross-origin; from a local build it is your own machine.

API key or bearer token (optional, stored in this tab only)

Public lookups

No key, no account. Rate limited per IP.

Returns the registration record for a domain, from RDAP where the
registry publishes it and port-43 WHOIS otherwise. Both paths return the
same shape.

`parsed.confidence` is derived from what was actually observed: 0 when
nothing could be read, 0.5-0.95 otherwise. A 404 means no record was
reachable, which is a valid answer and is reported rather than being
returned as an empty success.

Authentication

no credentials

Parameters

Name	Type	In	Notes
`domain`	string	query · required

Responses

Status	Meaning
`200`	Registration record
`400`	Invalid domain
`404`	No registration record could be read
`429`	Rate limited

domain *

Authentication

no credentials

Parameters

Name	Type	In	Notes
`domain`	string	query · required

Responses

Status	Meaning
`200`	DNS
`400`	Invalid domain
`429`	Rate limited

domain *

Authentication

no credentials

Parameters

Name	Type	In	Notes
`ip`	string	query · required

Responses

Status	Meaning
`200`	IP
`400`	Invalid IP
`429`	Rate limited

ip *

Investigations

Run and export investigations.

Authentication

X-API-Key: wv_…

Parameters

Name	Type	In	Notes
`target`	string	query · required

Responses

Status	Meaning
`200`	Investigation
`400`	Invalid target
`401`	Missing API key
`429`	Rate limited

target *

Authentication

X-API-Key: wv_…

Parameters

Name	Type	In	Notes
`target`	string	query · required

Responses

Status	Meaning
`200`	text/event-stream
`400`	Invalid target
`429`	Rate limited

target *

Authentication

X-API-Key: wv_…

Parameters

Name	Type	In	Notes
`target`	string	query · required
`format`	string	query · optional · default `json`

Responses

Status	Meaning
`200`	Report

target * format

Authentication

X-API-Key: wv_…

Request body

Field	Type	Required
`targets`	array	yes
`format`	string · json \| csv	no

Content-Type: application/json

Responses

Status	Meaning
`200`	Bulk results

JSON body

Authentication

X-API-Key: wv_…

Request body

Field	Type	Required
`targets`	array	yes
`domains`	array	no

Content-Type: application/json

Responses

Status	Meaning
`200`	Comparison results with shared infrastructure

JSON body

Authentication

Authorization: Bearer <jwt>

Request body

Field	Type	Required
`query`	string	yes
`invId`	integer	no

Content-Type: application/json

Responses

Status	Meaning
`200`	Parsed answer

JSON body

History & triage

Saved investigations, notes, and finding status.

One of the four allowed states. Anything else is rejected with
`400 INVALID_STATUS` — the list is validated against an allowlist rather
than trusted, so a typo cannot write an arbitrary string into the
database.

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`invId`	integer	path · required
`findingId`	string	path · required

Request body

Field	Type	Required
`status`	string · New \| Reviewed \| Dismissed \| Confirmed	yes

Content-Type: application/json

Responses

Status	Meaning
`200`	Status updated
`400`	Status not in the allowed set
`404`	Investigation not found or not owned by this user

JSON body

invId * findingId *

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`target`	string	query · optional
`limit`	integer	query · optional · default `20`

Responses

Status	Meaning
`200`	History page

target limit

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`from`	integer	query · required
`to`	integer	query · required

Responses

Status	Meaning
`200`	Diff

from * to *

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`id`	integer	path · required

Responses

Status	Meaning
`200`	Investigation

id *

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`invId`	integer	path · required

Responses

Status	Meaning
`200`	Notes

invId *

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`invId`	integer	path · required

Request body

Field	Type	Required
`kind`	string	yes
`ref_id`	string	no
`body`	string	yes

Content-Type: application/json

Responses

Status	Meaning
`201`	Created

JSON body

invId *

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`invId`	integer	path · required

Responses

Status	Meaning
`200`	Finding states

invId *

Monitoring

Watch targets and read alerts.

Authentication

Authorization: Bearer <jwt>

Responses

Status	Meaning
`200`	Monitors

Authentication

Authorization: Bearer <jwt>

Request body

Field	Type	Required
`target`	string	yes
`interval_hours`	integer	no

Content-Type: application/json

Responses

Status	Meaning
`201`	Created

JSON body

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`id`	integer	path · required

Responses

Status	Meaning
`204`	Deleted

id *

Authentication

Authorization: Bearer <jwt>

Responses

Status	Meaning
`200`	Alerts

Account

Sessions, API keys, usage.

Authentication

no credentials

Request body

Field	Type	Required
`email`	string	yes
`password`	string	yes

Content-Type: application/json

Responses

Status	Meaning
`201`	Created
`409`	Email exists

JSON body

Authentication

no credentials

Request body

Field	Type	Required
`email`	string	yes
`password`	string	yes

Content-Type: application/json

Responses

Status	Meaning
`200`	JWT + cookie + active apiKey (full value
`401`	Invalid credentials

JSON body

Authentication

Authorization: Bearer <jwt>

Responses

Status	Meaning
`200`	User + masked apiKeys

Destroys the server-side session and expires the cookie. Takes no body and
no Authorization header — the session cookie is the only thing being
presented, so requiring a bearer token here would be circular.

Safe to call when already logged out; it is idempotent.

Authentication

no credentials

Responses

Status	Meaning
`200`	Session cleared

Erases the account and everything referencing it — API keys, usage
records, investigations, triage notes, finding states, monitors,
alerts and failed-login counters — in a single transaction. There is no
undo and no soft-delete.

Always targets the caller's own account. There is no path parameter, so
an authenticated caller cannot name anyone else's account.

An issued JWT stays cryptographically valid until it expires, but
resolves to nothing afterwards because the user row it points at is
gone. API keys are revoked immediately by the same transaction.

Returns 204 if the account was already absent, which is a success: the
requested end state holds.

Authentication

Authorization: Bearer <jwt>

Responses

Status	Meaning
`200`	Account deleted
`204`	Account was already absent
`401`	Not authenticated

Authentication

Authorization: Bearer <jwt>

Request body

Field	Type	Required
`name`	string	no
`tier`	string	no

Content-Type: application/json

Responses

Status	Meaning
`201`	Key created (full value in response)

JSON body

Authentication

Authorization: Bearer <jwt>

Parameters

Name	Type	In	Notes
`id`	integer	path · required

Responses

Status	Meaning
`204`	Revoked

id *

Authentication

Authorization: Bearer <jwt>

Request body

Field	Type	Required
`webhook_url`	string	no

Content-Type: application/json

Responses

Status	Meaning
`200`	Saved

JSON body

Authentication

Authorization: Bearer <jwt>

Responses

Status	Meaning
`200`	Usage counters

System

Health and metrics. Unauthenticated.

Authentication

no credentials

Responses

Status	Meaning
`200`	OK

Authentication

no credentials

Responses

Status	Meaning
`200`	Ready
`503`	Not ready

Authentication

no credentials

Responses

Status	Meaning
`200`	Metrics