Any Guardrails on profile Access(entities endpoint) API using via programmatically Hi Community ,@abhi_tiwa_19 , @DavidRoss91 , @bjoern__koth , @Devyendar , @RiteshGA @DineshK We have multiple events are generated from the source, we plan to ingest only a specific event. To achieve this, we intend to use the Profile Access API to verify whether a particular transaction event already exists for a profile in AEP.If the transaction event is not present based on the Profile API response, the event will then be ingested into AEP via the HTTP Streaming Endpoint.Reference:https://experienceleague.adobe.com/en/docs/experience-platform/profile/api/entitieshttps://developer.adobe.com/experience-platform-apis/references/profile#operation/retrieveEntityAdditionally, are there any guardrails, soft limits, or hard limits associated with the usage of this API endpoint?Any suggestions would be appreciated Thank You Reshmika