Clarification would definitely be good. The sdk has a much different version number than the oauth api version in current use. documentation also provides for separate examples because the sdk is structured completely differently than the current api and looks nothing like the examples for the current api. So in documentation on the right where code examples are available, there is the options for PHP, PHP iSDK, XML-RPC and Python. REST has it’s own interactive docs page. The PHP goes over the oauth version (current). The PHP iSDK goes over the oldest version (using app key). XML-RPC and REST are more obvious. However, and I’m 100 percent certain of this, the documentation has only, within the past week, been changed to show oauth for the sdk as well as it showed the app key use up until then…this is a very recent change but it still remains that the use of the sdk differs from the php api version in current use.
example
to add a contact with the sdk you would instantiate the object and then make the call
$app->addWithDupCheck(array(‘FirstName’ => ‘test’, ‘LastName’ => ‘test’, ‘Email’ => ‘test@test.com’), ‘EmailAndName’);
The current api use looks like this:
$infusionsoft = new \Infusionsoft\Infusionsoft(array(
‘clientId’ => CLIENT_ID,
‘clientSecret’ => CLIENT_SECRET,
‘redirectUri’ => REDIRECT_URL,
));
$infusionsoft->refreshAccessToken();
$infusionsoft->contacts()->addWithDupCheck($data, $dupCheckType)
The point is that there is a clear structural difference (including the absence of ->where in the sdk version)