Forecast Parquet Monthly Exports

Guidance
,
1

Hello,

I’m trying to get the monthly forecast volumes through the new parquet endpoint but I’m getting the error message b’{“name”:“ExportError”,“message”:“Request data is required and must be an object”,“details”:{}}’

My payload was this:

payload = {
“exportType”: “monthlyForecastVolumeExport”,
“fileType”: “parquet”,
“projectId”: “67bf36e7550ef8145e877089”,
“forecastId”: “68629f6d41ced75e209b4ffc”
}
My endpoint was POST - https://api.combocurve.com/v1/exports

Am I supposed to ping a different endpoint before trying these one? Am i missing some other information?

Thanks for the help!

2

This message is returned if you are not passing an object as your payload.

Here I am passing the object

image
image1107×696 41.4 KB

Here I am passing an array

image
image1108×701 36.8 KB

Can you run your debugger and set a break point to double-check that you are passing the object you mentioned in the payload?

The payload you sent is correct so you should be getting something other than a 400 back.
{
“exportType”: “monthlyForecastVolumeExport”,
“fileType”: “parquet”,
“projectId”: “67bf36e7550ef8145e877089”,
“forecastId”: “68629f6d41ced75e209b4ffc”
}

3

Thanks! that was one of the problems, now I got a different error :smile:

b’{“name”:“ExportFilesNotFoundError”,“message”:“No files found”,“details”:{“exportType”:“monthlyForecastVolumeExport”,“fileType”:“parquet”,“projectId”:“67bf36e7550ef8145e877089”,“forecastId”:“68629f6d41ced75e209b4ffc”}}’

Is this another simple fix?

Thanks!

4

No worries! You need to have whoever is running the forecasts to export it so that external sources can pull it. This can be done by

  1. Going into the project 67bf36e7550ef8145e877089 and forecast 68629f6d41ced75e209b4ffc, then clicking on Forecast Options > Export Forecast Volumes (CSV)

image
image1901×979 218 KB

  1. After your export settings are correct, make sure that the File Typle is External Source
    Then click the Export button. Depending on the number of wells in the forecast, you may need to wait a couple of minutes for the files to process.

image
image963×964 36.3 KB

After you have followed these steps, your parquet should be accessible via the Exports endpoint.

5

I see, thanks for the reply!

Are there any plans to make this “Export to External Sources” available to the API? or maybe to have this endpoint trigger it when called? Having the manual step in between is not ideal for an automated pull/workflow.

6

There are definitely some considerations being given to these ideas. Currently, we have a pretty packed roadmap as far as integrations go. If/when this gets put on the roadmap I’ll let you know.

7

@HGantz

I finally got around to testing the parquet files. Blazing fast! I pulled in 15MM rows from a daily forecast in less than 30 seconds. Thanks for recommending I try this out!

1 Like
8

Love to hear it! We’re also building an async API endpoint to kick off Forecast Parameters exports and return a Parquet. This opens the door to kicking off the other forecast exports via the API, removing the requirement of using the UI.

1 Like