API Changelog
Stay up to date with the latest API changes, new features, and deprecation notices.
HTTP Basic Auth for API credentials
Authorization: Basic is accepted everywhere X-API-KEY is. Standard form is username=apiKey and password=apiSecret. The TAXII/Sentinel form (any username, password = Base64 credential) still works.
- curl -u apiKey:apiSecret works on /check, blocklists, TAXII, and the rest of the API
- Appliances that cap a single API-key field at 64 characters can use Basic Auth
- Legacy username api + Base64 password remains valid
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
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.