For the api.combocurve.com/v1/projects/:projectId/forecasts/:forecastId/monthly-volumes endpoint, I’m trying to pass the ‘well’ parameter filter. It looks like it will only accept a single well, not a list of wells. Is that correct? If so, any plans allow multiple wells in that filter?
You’re absolutely right that today the well filter only accepts a single ID—and we can absolutely look at extending it to a list in the future. The main reason we’ve held off so far is payload bloat. The response payload would quickly balloon into multiple megabytes. Large responses like that can lead to:
- Slow network transfers
- Higher memory usage on both server and client
- Increased latency as the server serializes and the client parses massive JSON
Thanks, Danny—appreciate the quick response. I noticed the monthly production endpoint does allow passing multiple well IDs, so I was hoping the same might apply for forecasts, but totally understand the concerns around payload size.
On a similar topic… A general challenge I’ve run into when pulling forecasts from the API (daily/monthly forecasts and type curves) is that the data often extends 50+ years depending on the technical cutoff, which makes the payloads balloon quickly.
A helpful feature down the road might be a years or months parameter that lets us limit the forecast range from the start date—something like “return only the first X months or years.” For my current use case (a type curve support slide builder), I really only need the first 3–5 years of forecast data.