Hi Steven, the Endpoint should be live now.
Please refer to this link for documentation on the endpoint [ComboCurve REST API]. And as always, if something comes up with the endpoint that needs discussing let us know and we’ll get to the bottom of it.
Just got it tested, looks good. Thank you so much for all of your help!
@hkong-cc one small issue I am running into here is accessing the date field. Each time I try to access is I get a 500 error, when I leave it out, my function runs as expected and I’m able to output data.
Any suggestions on how I can better access this field?
@StevenDestine For the date column, it should automatically populate even if you leave it out as it is a default column.
due to the width of the final output table, I hand selected the columns I wanted. When I put ‘date’ in here, it errors out. Either way, ‘date’ is not populating for me. ‘created_at’ is but I specified it here, and it outputs as a json field. The only default fields that I’m getting, that I didn’t specify, are combo_name and well_id.
I can share the rest of the code that creates this function if that would be helpful.
That’s strange, date should be automatically outputted along side the user-defined columns. Maybe we can work this out on a call, do you know who your usual customer support representative is, and if not, could you ask one of the engineers who use CC who they usually are in touch with?
