A client library for the Xero API, wrapping Guzzle and ORM-like models.
This library was developed for the traditional Private, Public and Partner applications, but is now based on OAuth 2 scopes.
- PHP 5.6+
Using composer:
composer require calcinai/xero-php
There is now only one flow for all applications, which is most similar to the legacy Public application. All applications now require the OAuth 2 authorisation flow and specific organisations to be authorised at runtime, rather than creating certificates during app creation.
As there is now only one type of application, you now create a generic XeroPHP\Application
with your access token and tenantId, from this
point onward, all your code should remain the same.
Before resource requests can be made, the application must be authorised. The authorisation flow will give you an access token and a
refresh token. The access token can be used to retrieve a list of tenants (Xero organisations) which the app is authorised to query, then,
in conjunction with the desired tenantId, you can instantiate a XeroPHP\Application
to query the API relating to a specific organisation.
For applications that require long-lived access to organisations, the refresh flow will need to be built in to catch and expired access token and refresh it.
Usage is the same as The League's OAuth client, using \Calcinai\OAuth2\Client\Provider\Xero
as the provider.
session_start();
$provider = new \Calcinai\OAuth2\Client\Provider\Xero([
'clientId' => '{xero-client-id}',
'clientSecret' => '{xero-client-secret}',
'redirectUri' => 'https://example.com/callback-url',
]);
if (!isset($_GET['code'])) {
// If we don't have an authorization code then get one
// Additional scopes may be required depending on your application
// additional common scopes are:
// Add/edit contacts: accounting.contacts
// Add/edit attachments accounting.attachments
// Refresh tokens for non-interactive re-authorisation: offline_access
// See all Xero Scopes https://developer.xero.com/documentation/guides/oauth2/scopes/
$authUrl = $provider->getAuthorizationUrl([
'scope' => 'openid email profile accounting.transactions'
]);
$_SESSION['oauth2state'] = $provider->getState();
header('Location: ' . $authUrl);
exit;
// Check given state against previously stored one to mitigate CSRF attack
} elseif (empty($_GET['state']) || ($_GET['state'] !== $_SESSION['oauth2state'])) {
unset($_SESSION['oauth2state']);
exit('Invalid state');
} else {
// Try to get an access token (using the authorization code grant)
$token = $provider->getAccessToken('authorization_code', [
'code' => $_GET['code']
]);
//If you added the openid/profile scopes you can access the authorizing user's identity.
$identity = $provider->getResourceOwner($token);
print_r($identity);
//Get the tenants that this user is authorized to access
$tenants = $provider->getTenants($token);
print_r($tenants);
}
You can then store the token and use it to make requests against the api to the desired tenants
OAuth scopes, indicating which parts of the Xero organisation you'd like your app to be able to access. The complete list of scopes can be found here.
$authUrl = $provider->getAuthorizationUrl([
'scope' => 'bankfeeds accounting.transactions'
]);
// Requires scope offline_access
$newAccessToken = $provider->getAccessToken('refresh_token', [
'refresh_token' => $existingAccessToken->getRefreshToken()
]);
Once you've got a valid access token and tenantId, you can instantiate a XeroPHP\Application
. All the examples below refer to models
in the XeroPHP\Models\Accounting
namespace. Additionally, there are models for PayrollAU
, PayrollUS
, Files
, and Assets
.
Refer to the examples for more complex usage and nested/related objects.
Create a XeroPHP instance (sample config included):
$xero = new \XeroPHP\Application($accessToken, $tenantId);
$contacts = $xero->load(Contact::class)->execute();
foreach ($contacts as $contact) {
print_r($contact);
}
Load collection of objects, for a single page, and loop through them (Why?)
$contacts = $xero->load(Contact::class)->page(1)->execute();
foreach ($contacts as $contact) {
print_r($contact);
}
Search for objects meeting certain criteria
$xero->load(Invoice::class)
->where('Status', Invoice::INVOICE_STATUS_AUTHORISED)
->where('Type', Invoice::INVOICE_TYPE_ACCREC)
->where('Date', 'DateTime(2020,11,25)')
->execute();
$xero->load(Invoice::class)
->where('Date >= DateTime(2020,11,25)')
->where('Date < DateTime(2020,12,25)')
->execute();
Load resources by their GUID
$contact = $xero->loadByGUID(Contact::class, $guid);
Populate resource parameters with their setters
$contact = new Contact($xero);
$contact->setName('Test Contact')
->setFirstName('Test')
->setLastName('Contact')
->setEmailAddress('[email protected]');
// Requires scope accounting.contacts to add/edit contacts
$contact->save();
If you have created a number of objects of the same type, you can save them all in a batch by passing an array to $xero->saveAll()
.
From v1.2.0+, Xero context can be injected directly when creating the objects themselves, which then exposes the ->save()
method. This is necessary for the objects to maintain state with their relations.
If you are saving several models at once, by default additional model attributes are not updated. This means if you are saving an invoice with a new contact, the contacts ContactID
is not updated. If you want the related models attributes to be updated you can pass a boolean flag with true
to the save method.
$invoice = $xero->loadByGUID(Invoice::class, '[GUID]');
$invoice->setContact($contact);
$xero->save($invoice, true);
$attachments = $invoice->getAttachments();
foreach ($attachment as $attachment) {
//Do something with them
file_put_contents($attachment->getFileName(), $attachment->getContent());
}
//You can also upload attachemnts
// Requires scope accounting.attachments
$attachment = Attachment::createFromLocalFile('/path/to/image.jpg');
$invoice->addAttachment($attachment);
To set the IncludeOnline
flag on the attachment, pass true
as the second parameter for ->addAttachment()
.
Models that support PDF export will inherit a ->getPDF()
method, which returns the raw content of the PDF. Currently this is limited to Invoices and CreditNotes.
The unit price decimal place precision (the unitdp
parameter) is set via a config option:
$xero->setConfigOption('xero', 'unitdp', 3);
If you are receiving webhooks from Xero there is Webhook
class that can help with handling the request and parsing the associated event list.
// Configure the webhook signing key on the application
$application->setConfig(['webhook' => ['signing_key' => 'xyz123']]);
$webhook = new Webhook($application, $request->getContent());
/**
* @return int
*/
$webhook->getFirstEventSequence();
/**
* @return int
*/
$webhook->getLastEventSequence();
/**
* @return \XeroPHP\Webhook\Event[]
*/
$webhook->getEvents();
To ensure the webhooks are coming from Xero you must validate the incoming request header that Xero provides.
if (! $webhook->validate($request->headers->get('x-xero-signature'))) {
throw new Exception('This request did not come from Xero');
}
Your request to Xero may cause an error which you will want to handle. You might run into errors such as:
HTTP 400 Bad Request
by sending invalid data, like a malformed email address.HTTP 503 Rate Limit Exceeded
by hitting the API to quickly in a short period of time.HTTP 400 Bad Request
by requesting a resource that does not exist.
These are just a couple of examples and you should read the official documentation to find out more about the possible errors.
This library will parse the response Xero returns and throw an exception when it hits one of these errors. Below is a table showing the response code and corresponding exception that is thrown:
HTTP Code | Exception |
---|---|
400 Bad Request | \XeroPHP\Remote\Exception\BadRequestException |
401 Unauthorized | \XeroPHP\Remote\Exception\UnauthorizedException |
403 Forbidden | \XeroPHP\Remote\Exception\ForbiddenException |
403 ReportPermissionMissingException | \XeroPHP\Remote\Exception\ReportPermissionMissingException |
404 Not Found | \XeroPHP\Remote\Exception\NotFoundException |
500 Internal Error | \XeroPHP\Remote\Exception\InternalErrorException |
501 Not Implemented | \XeroPHP\Remote\Exception\NotImplementedException |
503 Rate Limit Exceeded | \XeroPHP\Remote\Exception\RateLimitExceededException |
503 Not Available | \XeroPHP\Remote\Exception\NotAvailableException |
503 Organisation offline | \XeroPHP\Remote\Exception\OrganisationOfflineException |
See: Response codes and errors documentation
To catch and handle these exceptions you can wrap the request in a try / catch block and deal with each exception as needed.
try {
$xero->save($invoice);
} catch (NotFoundException $exception) {
// handle not found error
} catch (RateLimitExceededException $exception) {
// handle rate limit error
}