Expand my Community achievements bar.

SOLVED

What is the limitation on inbound API calls to AEP/AJO

Avatar

Level 1

I saw the document shows only batch process limitation is 4k to 5k and its tied to streaming.  What about HTTP API inbound requests?  The below link is related to batch and streaming only 

 

https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/guardrails

Any idea what is the limitation for real time? are those process through HTTP or is it a streaming process

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@vindra Here goes the details for AEP streaming sources (Enterprise connecters will have different entitlements) and these are all tenant level not sandbox level.

 

  • For data lake ingestion, the system supports between 4000 to 5000 requests per second.
  • For profile or streaming segmentation ingestion, the system supports a maximum of 1500 requests per second.

These limits apply independently to their respective processes. So, if you’re ingesting data to both the data lake and profiles/streaming segmentation simultaneously, each process will adhere to its own limit.

 

~cheers,

NN.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@vindra Here goes the details for AEP streaming sources (Enterprise connecters will have different entitlements) and these are all tenant level not sandbox level.

 

  • For data lake ingestion, the system supports between 4000 to 5000 requests per second.
  • For profile or streaming segmentation ingestion, the system supports a maximum of 1500 requests per second.

These limits apply independently to their respective processes. So, if you’re ingesting data to both the data lake and profiles/streaming segmentation simultaneously, each process will adhere to its own limit.

 

~cheers,

NN.