node-xero
NodeJS Client for the Xero API.
Supports all application types:
- Private - apps that can only connect to a single organisation
- Public - apps that can connect to any organisation, but only for 30 minutes at a time
- Partner - approved apps that can automatically refresh tokens
Features
- v3.0.0
- all accounting endpoints
- generic methods (
get
, put
, post
, delete
) for calling any unsupported endpoints
Installation
This SDK is published as an npm package called xero-node
.
npm install --save xero-node
Configuration
Sample configuration files for various application types are in the integration test directory.
Parameter | Description | Mandatory | Default |
---|
consumerKey | The consumer key that is required with all calls to the Xero API | True | - |
consumerSecret | The secret key from the developer portal that is required to authenticate your API calls | True | - |
callbackBaseUrl | The callback that Xero should invoke when the authorization is successful | False | null |
privateKeyPath | The filesystem path to your privatekey.pem file to sign the API calls | False | null |
redirectOnError | Whether Xero Auth should redirect to your app in the event the user clicks 'Cancel' | False | true |
Usage
const XeroClient = require('xero-node').AccountingAPIClient;
const config = require('/some/path/to/config.json');
const xeroClient = new XeroClient(config);
let invoices = xeroClient.invoices.get()
console.log("Number of Invoices: " + invoices.length);
Examples
Contributing
Local development
There are lots of TODOs in code and on our GitHub Projects kanban board - feel free to pick one off.
After you clone the repository, run npm install
to install required dependencies.
Running the tests
- Copy
private-config-example.json
to private-config.json
in the integration test directory. - Overwrite the example values with your own from the Developer Portal.
- (Do the same for
partner-config-example.json
if required.) - Run
npm test
Project Philosophies
-
A simple and intuitive interface.
eg:
PUT https://api.xero.com/api.xro/2.0/ContactGroups/b05466c8-dc54-4ff8-8f17-9d7008a2e44b/Contacts
becomes:
xero.contacts.contactGroups.create(contact)
Matching SDK methods names to endpoints, allows consumers to read the official API documentation and translate it to SDK method calls quickly.
That rather than using HTTP verbs (.put()
, .post()
etc) the SDK will use actions. Example get()
, create()
,delete()
, update()
. This abstracts away Xero's funny PUT
vs POST
.
-
A simple and single OAuth flow. Rather than automatically refreshing tokens, the SDK we will expose methods which allow the OAuth methods eg Refreshing Tokens etc. Consideration is also being made to OAuth2.
-
Abstracted underlyting OAuth/HTTP lib. This will allow swapping it out if we needed. The SDK won't bleed the OAuth libs exception types onto the consumer when it hits a 500/400 etc. Having a OAuth/HTTP layer will allow reuse and extension to other APIs (Payroll, Expenses etc).
-
Minimal to no entity/request/response validation. A consumer will pass in JSON and get JSON out. There will be no manipulation of data along the way. Helper methods if asked for will be provided by a separate module. This will reduce maintenance costs.
-
Unit tests!
-
Writing the SDK in Typescript will allow us to provide TS types for the API's contracts, and it's what we use internally at Xero. This will also aid in self-generated docs.
Maintainers
@philals @iamam34 @bryanlloydtee @dannyvincent @dupski