Changelog

API Changelog

Stay up to date with the latest API changes, new features, and deprecation notices.

v3.0.0Breaking Change2026-03-17

Canonical API host and paths (Rust)

Public REST API lives at https://api.ismalicious.com with root paths (/check, /bulk/check, …). Docs updated to match.

  • Authentication: X-API-KEY = Base64(apiKey:apiSecret) — not Authorization: Bearer for API keys
  • Single lookup: GET /check?query= — removed /v1/lookup/... examples
  • Bulk: POST /bulk/check JSON { entities[], enrichment? }
  • Progressive check: SSE GET /check/stream?query= (or /stream)
  • User webhooks: CRUD at /user/webhooks for paid plans; OpenAPI at /openapi.json
v2.3.0Deprecation2024-01-15

Legacy streaming docs

Earlier marketing copy referenced WebSocket and stream.ismalicious.com. The supported progressive API is SSE on api.ismalicious.com as documented today.

  • Use GET https://api.ismalicious.com/check/stream?query= for phased check streams
v2.2.0Deprecation2024-01-08

Legacy bulk marketing

Older pages described async 1M-item jobs; current bulk API is synchronous POST /bulk/check with plan-based batch sizes.

  • See GET /bulk/check for limits; POST returns results[] per entity in one response
v2.1.1Bug Fix2024-01-02

Bug Fixes

Various bug fixes and performance improvements.

  • Fixed pagination cursor issues
  • Improved WHOIS data parsing
  • Better handling of IDN domains
v2.1.0New Feature2023-12-20

Ransomware Intelligence API

New endpoints for ransomware tracking and IOCs.

  • Ransomware group profiles endpoint
  • Victim tracking with alerts
  • IOC feeds for ransomware campaigns
  • Real-time leak site monitoring
v2.0.0Breaking Change2023-12-01

API v2 Release

Major version release with breaking changes. v1 deprecated.

  • New response format with enrichment data
  • Unified endpoint structure
  • Rate limit changes
  • v1 deprecated (sunset: 2024-06-01)

Why Track API Changes?

Staying current with API changes ensures your integrations continue working smoothly and take advantage of new capabilities. Our changelog documents every feature addition, bug fix, and breaking change with detailed migration guidance. Subscribe to notifications so you're never caught off guard by deprecations or behavior changes.

Our Versioning Policy

We follow semantic versioning (semver) for our API: major versions indicate breaking changes, minor versions add new features without breaking existing integrations, and patch versions contain bug fixes. Breaking changes are announced at least 90 days in advance, and deprecated endpoints remain functional for a minimum of 6 months after deprecation notice.

Migration Support

When we introduce breaking changes, we provide comprehensive migration guides with code examples, before/after comparisons, and common pitfalls to avoid. Our support team is available to help enterprise customers plan and execute migrations. We also maintain compatibility shims where possible to ease the transition period.

Stay Updated

Subscribe to receive notifications about API changes.

Create Account