verified/verified-sdk-php

Verified API PHP SDK

Please note: This repository has been deprecated in favour of wcealliance/php-sdk, _(*1)

Verified API SDK for PHP

, _(*2)

Communicate with the Verified REST API using PHP, _(*3)

Install with Composer

If you're using Composer to manage dependencies, you can add the Verified SDK with it., _(*4)

{
  "require" : {
    "verified/verified-sdk-php": "dev-master"
  },
  "minimum-stability": "dev"
}

Install source from GitHub

The Verified SDK requires Unirest as a dependency. It also requires PHP v5.3+ and cURL extensions for PHP. Download the PHP library from Github, and require in your script like so:, _(*5)

To install the source code:, _(*6)

$ git clone git@github.com:verified/verified-sdk-php.git

And include it in your scripts:, _(*7)

// first include Unirest
require_once '/path/to/unirest-php/lib/Unirest.php';
// then include this
require_once '/path/to/verified-sdk-php/lib/Verified.php';

Usage

The main requirements for running this SDK are api_key and api_secret. Please make sure you have them before you proceed any further., _(*8)

The class can be configured in multiple ways, by sending in a configuration array during class instantiation:, _(*9)

// create a new instance
$config_array = array(
  "api_endpoint"   => "http://verifiedapi.org",
  "api_key"        => 'YOUR_API_KEY',
  "api_secret"     => 'YOUR_API_SECRET',
  "api_version"    => '1'
);
$verified = new Verified($config_array);

Or by using a more OOP approach:, _(*10)

$verified = new Verified();
$verified->setKey('YOUR_API_KEY')
  ->setSecret('YOUR_API_SECRET')
  ->setConfig('api_version', '1');

Configuration parameters other than api_key and api_secret have setter and getter methods:, _(*11)

// set a config param
$verified->setConfig('api_version', '1');
// get a config param
$version = $verified->getConfig('api_version');

Please Note: By default, the api_endpoint parameter is set to the live URL, to use sandbox mode, please use the sandbox url http://sandbox.verifiedapi.org., _(*12)

Making REST calls to API resources

Please see the Verified API docs for a list of available API resource endpoints. The class uses __call() magic method to work out which resource you are calling., _(*13)

For example:, _(*14)

// make a GET request to /user/user@email.com
$user = $verified->getUser('user@email.com');
// make a POST request to /user
$user = $verified->addUser(array('post_params'));
// make a PUT request to /user/user@email.com
$verified->editUser('user@email.com', array('post_params'));
// make a DELETE request to /user/user@email.com
$verified->deleteUser('user@email.com');

Calling sub-resources follow a similar camelCased pattern, for example:, _(*15)

// make a GET request to /user/user@email.com/trainingProfile/
$training_profile = $verified->getUserTrainingProfile('user@email.com');

In simple terms: - getXXX() maps to GET requests - addXXX() maps to POST requests - editXXX() maps to PUT requests - deleteXXX() maps to DELETE requests, _(*16)

Output data & Error handling

All data from the SDK are in plain PHP arrays. If a method call fails, the output is false., _(*17)

If you encounter the result of a query returning false, the error that occured can be obtained from the getError() method., _(*18)

A very simple error resilient code snippet follows:, _(*19)

$user = $verified->getUser('user@email.com');
if ($user == false) {
  $error = $verified->getError();
  if($error){
    throw new Exception($error['errorCode'] . $error['userMessage']);
  }
} else {
  //loop through the returned data
  //and do something with it
}

When calling PUT and POST endpoints (addXXXX() and editXXXX()), if the payload contains invalid data, data validation messages appear in the form of an array inside the error object:, _(*20)

array(
  'errorCode'   => '400',
  'userMessage' => 'Bad Request',
  'devMessage'  => array(
      'email'   => 'Invalid email address'
  )
)

Response Metadata

In addition to the special getter getError(), there is also another getter method for metadata. getMetadata() returns an array containing all the metadata that was sent with the response., _(*21)

Metadata usually contains the response status, offset/limit values and the total number of records returned. It also contains HATEOAS links which can be leveraged for paginating long lists., _(*22)

To obtain HATEOAS links only, another special getter getLinks() can be used. It returns just the HATEOAS links from a response., _(*23)