This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the customer wanted to know if we have full support for the wordpress REST API
Solution:
Unfortunately no we currently don't have full REST support. What we have currently is for exposing the custom post types to the api for view purposes only.
50% of people find this useful.
This support ticket is created 6 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Our next available supporter will start replying to tickets in about 0.83 hours from now. Thank you for your understanding.
Yes it is possible to update your CPT using the REST api as there is a setting now as you can see in the screenshot you provided to do enable the REST api for that CPT.
Has something changed from last year? I am trying to learn rest api but if it is not possible to update a custom post's fields, I should find another workaround and stop spending time to learn sth that I cannot use. That's why I am asking.
I reviewed this with the team to gain some more clarity on this.
Currently the REST function only exposes Custom Post Types to the REST API for viewing and not for the full REST operations. Secondly Custom Fields are not available in the REST Api.
Thats as much information I have for now. The next thing is that reference was made to the code that Adriano wrote here hidden link
But I can get in touch to see if there was any update on this.
Shane, please add my vote for the rest api support for custom fields. I believe that it would give much more power to toolset plugins and would help us build awesome applications. Thank you for providing the link from Adriano's code!
Same - I'd prioritize custom fields, as CPT are relatively useless without those even for READ, but at some point Toolset needs full REST support. Surprised and disappointed this isn't already integrated.
Geoffrey, I'm in the exact same boat as you. So frustrating!
As much as I'm a huge toolset fan and super excited about the new relationships feature, I'm building progressive web apps via headless WP and Toolset has become absolutely useless to me without full REST API support.
Such a shame to have to use ACF or other solutions because of this, especially considering REST is in core now!