We’re happy to announce the release of Version 2 APIs for EventLog Analyzer, now available with new endpoints, improved functionality, and expanded use cases.

To help users get started faster, we’ve also published ready-to-use Postman collections with sample requests and responses.

You can access the complete API documentation — including supported operations, request/response formats, and usage examples — via our updated API portal.

⚠️ Note: V1 APIs are deprecated, and no new authentication tokens can be created. Support for V1 APIs will continue until September 2026.

Why Migrate to Version 2 APIs

• Long-term Scalability: Standardized APIs are crucial for managing an application's growth. By following consistent design principles, the API structure remains organized and predictable, preventing it from becoming disorganised and unwieldy over time. This makes it easier to add new endpoints, resources, and functionalities without disrupting existing integrations, ensuring the API can support future demands efficiently.

• Data Consistency: Using standardised formats like ISO 8601 for dates ensures that data is represented uniformly across the entire system, reducing errors and integration issues.

• Improved Security and Compliance: Following established RFCs and ISO standards often aligns with security best practices, making the APIs more robust and easier to audit for compliance.

• Enhanced Maintainability: A consistent and predictable API structure makes it simpler for developers to understand, maintain, and debug the code, both for the API provider and its users.

• Reduced Integration Effort: Developers integrating with the API will find it easier to understand and use because the formats and conventions are familiar and follow industry best practices. This "developer-friendly" approach reduces the learning curve and speeds up implementation.

• Clearer Communication: A well-designed URI with a hierarchical structure and clear resource names makes the API self-documenting, allowing developers to intuit its purpose without needing extensive documentation.

• Interoperability: By adhering to global standards(ISO, RFC, etc.) , the API can more easily communicate with other systems and platforms that also follow these conventions.