Sitecore Content Hub is an extremely versatile and power digital asset management (DAM) platform.

The core part of the platform is the DAM which is elevated when the additional areas are activated to improve the experience for users. These areas are:

• Content Management Platform (CMP)
• Product Content Management (PCM)
• Sitecore Content Publisher (W2P)
• Marketing Resource Management (MRM)

They all improve the content lifecycle with additional fully integrated features. Every part interconnected under a single powerful API.

However…

Users will use more of the platform and the additional areas. Depending on the needs you will then have additional integrations. More integrations will increase the use of the API or the Content Hub SDK. All potentially making more requests.

This is a good problem to have as users are using the platform. Limits are just something you need to be mindful of.

---

Naturally Sitecore have API limits in place to protect the Content Hub instances from over consumption of requests. If thresholds are exceeded then throttling will start. The following page is the official information from Sitecore – https://docs.stylelabs.com/contenthub/4.1.x/content/integrations/best-practices/throttling.html

The main take away points are:

• By default there is a rate limit of 15 calls per second (per API integration user).
  • Customers can opt to increase this in 15 calls per second increments
  • Speak to your Sitecore Account Manager of Customer Success Manager to find out steps to increase
• Content Hub SDK
  • It has embedded throttling, over the REST API
  • Built-in retry policy. By default, any call returning an HTTP 429 response is retried nine times. You can modify the RetryCount property of the retry policy as required.

This is something to be aware of incase you start getting requests that fail with a timeout.

I am currently working on a project where there are 100,000’s of entities that are updating on a daily basis. It has multiple integrations and data is exported every night to downstream systems.

We started to encounter thousands of 429 errors each night as we were going over the calls per second (in some cases 50 per second). This would cause Content Hub to defend and start blocking access to users. The issue is currently being resolved by re architecting the export processes and also limit calls where we can.

I hope this post is useful to someone who may encounter the same issues