Centralized Logging for Didit API Events with New Relic/Datadog

Streamlined ObservabilityCentralized logging platforms like New Relic and Datadog provide a unified view of all Didit API interactions, simplifying troubleshooting and performance monitoring across your identity verification workflows.

Proactive Issue DetectionBy aggregating and analyzing Didit API logs, you can set up alerts for anomalies, rate-limiting warnings, or authentication failures, enabling rapid response to potential issues before they impact users.

Enhanced Compliance & AuditingMaintain a comprehensive audit trail of all identity verification events, which is crucial for regulatory compliance and internal security policies, particularly when handling sensitive user data with Didit's ID Verification and AML Screening.

Didit's Developer-First ApproachDidit's clean APIs and structured event data make it exceptionally straightforward to integrate with any logging solution, ensuring a smooth setup for real-time monitoring and analysis of your identity verification processes.

The Criticality of Centralized Logging for API Integrations

In today's interconnected digital landscape, applications rely heavily on APIs for various functionalities. For services as crucial as identity verification, provided by platforms like Didit, the ability to monitor API interactions in real-time is not just a best practice—it's a necessity. Centralized logging solutions, such as New Relic or Datadog, offer a panoramic view of your system's health, allowing you to collect, aggregate, and analyze logs from all your services, including those interacting with the Didit API. This consolidated approach transforms raw log data into actionable insights, helping you to quickly identify and resolve issues, optimize performance, and maintain a high level of security and compliance.

Imagine a scenario where a user's ID Verification process fails. Without centralized logging, debugging this could involve sifting through multiple service logs, a time-consuming and error-prone task. With a solution like New Relic or Datadog, you can trace the entire transaction flow, from your application's request to the Didit API's response, pinpointing the exact point of failure within seconds. This level of visibility is indispensable for maintaining a smooth user experience and ensuring the reliability of your identity verification workflows.

Integrating Didit API Events with New Relic or Datadog

Integrating Didit API events into your centralized logging platform involves capturing the requests made to and responses received from the Didit API. Given Didit's developer-first approach, its clean APIs make this process remarkably straightforward. For example, when using Didit's ID Verification or Age Estimation products, every API call and its corresponding response generates valuable log data.

Capturing API Request and Response Data

When your application makes a call to a Didit endpoint, such as POST /v2/session/ for creating a new verification session or GET /v2/session/<id>/decision/ for retrieving a session decision, you should log key details. This includes the request timestamp, the specific endpoint accessed, the request payload (sanitized to remove sensitive PII), and crucially, the HTTP status code and response body from Didit.

For authentication, Didit uses API keys, which should always be kept server-side. Errors like a 401 Unauthorized response indicate an invalid or missing API key, which should be logged and alerted upon. Similarly, a 429 Too Many Requests response, indicating you've hit a rate limit, should trigger an alert and prompt an exponential backoff strategy in your client. Didit's API includes headers like X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset in 429 responses, providing valuable data for your logging and alerting systems.

Configuring Log Agents

Both New Relic and Datadog provide agents or libraries that can be easily integrated into your application's environment. These agents automatically collect logs from your application, process them, and forward them to the respective logging platform. You can configure these agents to parse your Didit API event logs, extracting critical fields like session IDs, workflow IDs, error messages, and decision outcomes. This structured logging enables powerful querying and visualization capabilities within New Relic or Datadog.

Leveraging Logs for Proactive Monitoring and Alerting

Once your Didit API event logs are flowing into New Relic or Datadog, you can unlock a wealth of monitoring and alerting capabilities:

• Performance Monitoring: Track API response times for Didit's various services, such as Passive & Active Liveness checks or 1:1 Face Match. Identify latency spikes and ensure your identity verification process remains swift and efficient.
• Error Rate Tracking: Monitor the frequency of HTTP 4xx and 5xx errors from the Didit API. Set up alerts for sudden increases in errors, especially for critical operations like ID Verification or AML Screening, to ensure continuous service availability.
• Rate Limit Management: Create dashboards to visualize your usage against Didit's API rate limits. Configure alerts when your X-RateLimit-Remaining drops below a certain threshold (e.g., 15%), allowing you to proactively adjust your traffic or request an override from Didit support.
• Security and Compliance Auditing: For compliance with regulations like GDPR, maintaining an auditable log of identity verification attempts and outcomes is crucial. Didit acts as a data processor, and you, as the data controller, can leverage these logs to demonstrate adherence to data protection policies. Didit also offers configurable data retention policies in the Business Console, allowing you to select a window from 1 month to 10 years, or unlimited, for your verification data.
• Deep Dive Troubleshooting: When an issue arises, use the powerful search and filtering capabilities of your logging platform to quickly isolate relevant Didit API events, analyze their context, and determine the root cause, whether it's a configuration error on your side or an unexpected response from an external service.

How Didit Helps

Didit is engineered to be an AI-native, developer-first identity platform, making integration with centralized logging solutions incredibly seamless. Our modular architecture means that each component, from ID Verification (OCR, MRZ, barcodes) to Passive & Active Liveness and AML Screening & Monitoring, provides clear, structured API responses that are easy to parse and log. Didit's commitment to structured identity data ensures that every event provides rich context, making your logs more valuable for analysis in New Relic or Datadog.

Furthermore, Didit's Free Core KYC offering means you can start building and integrating your identity verification workflows without upfront costs, allowing you to allocate resources to robust logging and monitoring infrastructure. Our no-code Business Console allows you to configure workflows and data retention policies, further simplifying your operational overhead. By providing transparent API responses and detailed error messages, Didit empowers you to build comprehensive observability into your identity verification processes, ensuring stability, security, and compliance from day one.

Ready to Get Started?

Ready to see Didit in action? Get a free demo today.

Start verifying identities for free with Didit's free tier.