It would be very useful to have an API endpoint for ingesting source content in bulk, similar to how there is currently one for creating ANS content in bulk.
I am working on integrating the ANS mapping functionality to ingest stories and their associated images and galleries from a large news source. With the amount of stories we ingest and the need to make separate API calls for each image, story, and gallery, I fear we will go over the 800 request per minute.
In addition, just a single media-rich story can require >30 requests to fully ingest, running afoul of burst limits.
A /migrations/v3/content/source/bulk API endpoint would prevent this from happening.
Lowell Kissling
I have just learned that in addition to the 800 request per minute rate limit, there is also a burst limit that I consistently hit when making >33 requests at a time. This burst limit makes the need for a bulk endpoint much greater.
I have just learned that in addition to the 800 request per minute rate limit, there is also a burst limit that I consistently hit when making >33 requests at a time. This burst limit makes the need for a bulk endpoint much greater.