According to the Management API v2 documentation for /api/v2/event-streams, the field id is defined as the unique identifier for the event stream. Based on this, we have implemented id as the primary key on our side.
However, we are receiving id as null, which is causing primary key issues and causing connection failures.
Welcome to the Auth0 Community!
Just to double check, are you using the Event Streams endpoint in order to integrate with an AWS EventBridge or are you trying to integrate with other log management tools (ex: Datadog, Webhooks, Splunk)?
If you are using it for AWS EventBridge or anything similar, then the null value might be a caused by a created stream process which did not complete (either it is stuck in a pending or failed validation status) and the backend record was created without finalizing.
Can you let me know if your Auth0 logs include the event stream ID and if they are successful or not? Also, does the same happen when using the Management API page you have linked above?
If you can confirm that these kind of entries are invalid and can be removed, you can configure your integration to filter them out, otherwise, you can attempt to use the name as a fallback key.
Please take note that the Event Streams feature is in Early Access and it might not behave accordingly at this time until its full release.
Kind Regards,
Nik
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.