The 10-Product-a-Day API Limit That Changed How I Ship Digital Products

Description and use

The author faced a 10‑product daily creation cap on a marketplace API. He built a scheduled, idempotent uploader that records each successful creation in a ledger, stops when the cap is hit, and resumes the next day, raising shipped products from 10 to 39 without duplicates.

Problem

An uploader could create many products in one batch, but after ten creations it silently failed with no error message or rate‑limit header.

Outcome

The new workflow allowed the author to ship 39 products instead of 10 without duplicates, improving business throughput.

Workflow

• Read ledger of already live products
• Upload next few items that are not in ledger
• Record each new item upon API confirmation
• Stop when the 10‑product cap is hit
• Resume next day from where it left off

Evidence

I built an uploader that could create a hundred products in an afternoon. Then it started failing after ten.

Source

Just ten successes and then nothing, every time I tried a batch.

Source

The ledger is the whole trick. Without it, a job that dies halfway cannot tell what it already did, and you get duplicates.

Source