Identity exposure

Correlate breach, session, SIM swap and domain signals for one identity

Runs the breach and stolen-session checks for the supplied email (always), plus SIM swap when a phone is supplied and a domain lookalike sweep when a domain is supplied, then matches the resulting signal set against the same coordinated-attack-chain table the WhatsApp monitor uses in the background -- on demand, for any identity, in one call. A chain match (for example breach + SIM swap within the same identity) is a materially higher-confidence finding than either signal alone: attackers commonly combine credential theft with a SIM swap to intercept SMS 2FA.

Billing. $0.50 per successful call. Failed calls are never billed. Charged against prepaid credits when the balance covers it, otherwise metered to your card. Threat Intelligence subscribers and AWS Marketplace bundle customers call this at no extra charge.

Note. Each sub-check keeps its own failure behaviour -- a SIM swap check the carrier could not answer, or a session-risk query that failed, is reported as checked: false rather than folded into 'not present'. Only smishing_to_sim_swap and breach_otp_intercept can never fire here: both require an SMS or OTP event observed inside a monitored conversation, which this endpoint has no way to check for an arbitrary identity.

post/v1/metered/incident-timeline

Request

  • Base URL: https://api.relayshield.net
  • URL: https://api.relayshield.net/v1/metered/incident-timeline
  • Auth: one of:
    • API key in header X-RS-API-KEY
    • HTTP bearer

Request body

emailstring email required

Email address to check. Always run.

phonestring

E.164 phone number. Optional -- adds the SIM swap check.

domainstring

Domain to sweep for lookalikes. Optional -- adds the domain-lookalike check.

Example request

{
  "phone": "+14155551234",
  "domain": "acme.com"
}

Response

Success. ok is true and data holds the result.

oktrue required

Changes

No recorded changes to this operation across all 1 revision of this API.