API simply means application program interface. The details of what it does are not defined by simply using the term api.

Reading the documentation it is clear to me that this API is for accessing information on the current page.

This comes in handy for me because it makes it handy to get values from fields and set values in fields. It also enables me to dynamically alter one field based on a value entered into another field. For example, I can create a select field where the choices are dynamically generated based on the selection in another select field.

Thx for the wiki lookup on api.The details of what it does are not defined by simply using the term api.
No, you are right. Never the less, a certain expectation is associated with the term. That expectation is formed by the countless api’s out there.

If you want to use an “api” for syncing inputs… well you found your gem.
It still does not make sense to me to use and “api” to fetch informations which are already present.

Also thanks for the link you posted. I appreciate people that point others into the right direction.
I decided after all to not go with jquery but to use fetch in combination with acf to REST which i can recommend to anybody doing more then syncing inputs.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Welcome

Welcome to the Advanced Custom Fields community forum.

Browse through ideas, snippets of code, questions and answers between fellow ACF users

We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.