Keyword and redirect screening of URLs–to stay compliant.

Why payment and risk teams use it

• PSPs can POST a redirect or callback URL (e.g. after 3‑D Secure or wallet return) and receive structured results in milliseconds after our fetch completes—ready to plug into rule engines, velocity checks, or manual review queues.
• Each row in the response mirrors what you would see in our internal bulk scanner: input URL, whether the request redirected, final URL, keyword hits with categories, and match context snippets.
• This API is separate from our Full Report API (/api/analyze, /api/analyze-ip), which returns the complete website or IP intelligence report including hosting, SSL, reviews, and aggregate risk scoring.

Endpoint

POST https://osintintel.com/api/v1/keyword-scan

Body: JSON with a single field urls—a string containing one URL per line (same format as our bulk admin tool).

curl -sS -X POST "https://osintintel.com/api/v1/keyword-scan" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":"https://example.com/return\nhttps://another.example/path"}'

Example response JSON

Illustrative payload. rows aligns with the bulk keyword scan table: hits lists keyword, category, and context; redirected and redirectChain describe HTTP hops.

{
  "success": true,
  "count": 1,
  "maxUrls": 100,
  "durationMs": 2400,
  "avgMsPerUrl": 2400,
  "rows": [
    {
      "inputUrl": "https://checkout.example.com/order/12345/success",
      "finalUrl": "https://checkout.example.com/order/12345/success",
      "error": null,
      "redirected": false,
      "redirectChain": [
        { "url": "https://checkout.example.com/order/12345/success", "status": 200 }
      ],
      "hits": [
        {
          "keyword": "replica",
          "category": "Counterfeit & Replica",
          "context": "...luxury replica watches overnight..."
        }
      ]
    }
  ]
}