Just as summary above says, there doesn’t appear (yet) to be an API endpoint to get custom fields for the Opportunity table, nor does it appear that the schema for opportunities includes custom fields in its return body. Any plans to add it?
I’ve been looking at the API docs for the new REST API. Overall, I’m impressed with the changes you’re making-- abstracting a lot of the underlying database structure from what’s accessible from the outside (i.e. how addresses are now formatted into an array of sub-objects, rather than using fields on the base Contact object), presumably so you can make changes later without breaking third party code. It looks like working with Campaigns/Sequences etc is going to be much more intuitive from here on out as well.
I can fall back to XMLRPC to get the info for now, I’m just trying to reduce the number of detours I have to take as much as possible.