Any Guardrails on profile Access(entities endpoint) API using via programmatically

Question

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

ReshmikaPu · Accepted Answer

Hi Teamwas able to get the limits on Profile API accessthis is a limitation on producthttps://experienceleague.adobe.com/en/docs/experience-platform/sandbox/homehttps://helpx.adobe.com/legal/product-descriptions/adobe-experience-platform0.html#:~:text=Profile%20Activation.%C2%A0%C2%A0Customer%20may%20process%20up%20to%205%20Profile%20API%20Calls%20per%20Profile%20per%20year%20(e.g.%2C%20a%20Customer%20with%20a%20licensed%20entitlement%20of%201%20million%20Profiles%20could%20process%20up%20to%205%20million%20Profile%20API%20Calls%20per%20year%2C%20aggregated%20and%20not%20tied%20to%20each%20Profile)

DavidRoss91 · Answer

Hi ​@ReshmikaPuWhen using the Profile Service API, there is the possibilityof recently ingested events not being queryable right away in this case since you are looking at the profile store. It might make more sense to handle your deduplication of events outside of platform and then deciding what to bring in post that review

Sign up

Login with SSO

Login to the community

Login with SSO