These points above are indeed good examples regarding "forcing bad practices": If I have 3 free API calls after the API call, after the 3rd freebie, I can return it and call again for 1 core + 3 more that can branch off again. This is inefficient for BC, yet beneficial for end-users (thus, forcing bad practices since it costs and gives more if we avoid the pre and post hooks). If a workaround to save API costs would be more work for the user, and costs more for BC, that's a lose-lose. If such a "hole" exists, shouldn't it be repriced for that consideration to make it the win-win you folks want it to be?

Thank you very much

We'll look into it @Omar-Alzayed ... Paul.

@Paul-Winterhalder said in A few suggestions I have so far: . Would it be fair to say that those user's entities would have to have their ACL set to other: 1 so it's readable? Yes, that would be the case.