Currently, POST /v0/requirements only supports uploading a single requirement object per request. Attempts to send a bulk body shaped like { "requirements": [...] } return a 400 error.

This is inconsistent with POST /v0/forecasts, which supports bulk uploads of up to ~200 interval objects per request, enabling high-throughput workflows.

The impact: customers uploading large requirement grids are forced into a one-request-per-object pattern, significantly increasing runtime due to HTTP overhead — even with parallelisation and rate limiting.Currently, POST /v0/requirements only supports uploading a single requirement object per request. Attempts to send a bulk body shaped like { "requirements": [...] } return a 400 error.

This is inconsistent with POST /v0/forecasts, which supports bulk uploads of up to ~200 interval objects per request, enabling high-throughput workflows.

The impact: customers uploading large requirement grids are forced into a one-request-per-object pattern, significantly increasing runtime due to HTTP overhead — even with parallelisation and rate limiting.