A PHP library for Twinfield Integration. Use the Twinfield SOAP Services to have your PHP application communicate directly with your Twinfield account.
Install this Twinfield PHP library with Composer:
composer require 'php-twinfield/twinfield:^3.0'
You need to set up a \PhpTwinfield\Secure\AuthenticatedConnection
class with your credentials. When using basic
username and password authentication, the \PhpTwinfield\Secure\WebservicesAuthentication
class should be used, as follows:
$connection = new Secure\WebservicesAuthentication("username", "password", "organization");
Some endpoints allow you to filter on the Office, but for instance the BrowseData endpoint doesn't. For this you need to switch to the correct office before making the request, you can do this after authentication like so:
$office = Office::fromCode("someOfficeCode");
$officeApi = new \PhpTwinfield\ApiConnectors\OfficeApiConnector($connection);
$officeApi->setOffice($office);
In order to use OAuth2 to authenticate with Twinfield, one should use the \PhpTwinfield\Secure\Provider\OAuthProvider
to retrieve an \League\OAuth2\Client\Token\AccessToken
object, and extract the refresh token from this object. Furthermore, it is required to set up a default \PhpTwinfield\Office
, that will be used during requests to Twinfield. Please note: when a different office is specified when sending a request through one of the ApiConnectors
, this Office will override the default.
Using this information, we can create an instance of the \PhpTwinfield\Secure\OpenIdConnectAuthentication
class, as follows:
$provider = new OAuthProvider([
'clientId' => 'someClientId',
'clientSecret' => 'someClientSecret',
'redirectUri' => 'https://example.org/'
]);
$accessToken = $provider->getAccessToken("authorization_code", ["code" => ...]);
$refreshToken = $accessToken->getRefreshToken();
$office = \PhpTwinfield\Office::fromCode("someOfficeCode");
$connection = new \PhpTwinfield\Secure\OpenIdConnectAuthentication($provider, $refreshToken, $office);
For more information about retrieving the initial AccessToken
, please refer to: https://github.com/thephpleague/oauth2-client#usage
In order to communicate with the Twinfield API, you need to create an ApiConnector
instance for the corresponding
resource and use the get()
or list()
method.
The ApiConnector
takes a Secure\AuthenticatedConnection
object:
An example:
$connection = new Secure\WebservicesAuthentication("username", "password", "organization");
$customerApiConnector = new ApiConnectors\CustomerApiConnector($connection);
// Get one customer.
$office = Office::fromCode('office code');
$customer = $customerApiConnector->get('1001', $office);
// Get a list of all customers.
$customer = $customerApiConnector->listAll($office);
If you want to create or update a customer or any other object, it's just as easy:
$customer_factory = new ApiConnectors\CustomerApiConnector($connection);
// First, create the objects you want to send.
$customer = new Customer();
$customer
->setCode('1001')
->setName('John Doe')
->setOffice($office)
->setEBilling(false);
$customer_address = new CustomerAddress();
$customer_address
->setType('invoice')
->setDefault(false)
->setPostcode('1212 AB')
->setCity('TestCity')
->setCountry('NL')
->setTelephone('010-12345')
->setFax('010-1234')
->setEmail('[email protected]');
$customer->addAddress($customer_address);
// And secondly, send it to Twinfield.
$customer_factory->send($customer);
You can also send multiple objects in one batch, chunking is handled automatically.
In order to get financial data out of Twinfield like general ledger transactions, sales invoices, and so on, you can use the the browse data functionality. More information about the browse data functionality in Twinfield can be found in the documentation.
You can retrieve the browse definition of a browse code as follows. You don't need to retrieve the browse definition for getting the browse data. It's only for viewing the browse definition of a browse code to know exactly which columns are available.
$connector = new BrowseDataApiConnector($connection);
$browseDefinition = $connector->getBrowseDefinition('000');
You can retrieve the browse fields as follows. You don't need to retrieve the browse fields for getting the browse data. It's only for viewing the definitions of all browse fields so you now what you can expect when retrieving browse data.
$connector = new BrowseDataApiConnector($connection);
$browseFields = $connector->getBrowseFields();
You can retrieve browse data of a browse code as follows.
$connector = new BrowseDataApiConnector($connection);
// First, create the columns that you want to retrieve (see the browse definition for which columns are available)
$columns[] = (new BrowseColumn())
->setField('fin.trs.head.yearperiod')
->setLabel('Period')
->setVisible(true)
->setAsk(true)
->setOperator(Enums\BrowseColumnOperator::BETWEEN())
->setFrom('2013/01')
->setTo('2013/12');
$columns[] = (new BrowseColumn())
->setField('fin.trs.head.code')
->setLabel('Transaction type')
->setVisible(true);
$columns[] = (new BrowseColumn())
->setField('fin.trs.head.shortname')
->setLabel('Name')
->setVisible(true);
$columns[] = (new BrowseColumn())
->setField('fin.trs.head.number')
->setLabel('Trans. no.')
->setVisible(true);
$columns[] = (new BrowseColumn())
->setField('fin.trs.line.dim1')
->setLabel('General ledger')
->setVisible(true)
->setAsk(true)
->setOperator(Enums\BrowseColumnOperator::BETWEEN())
->setFrom('1300')
->setTo('1300');
$columns[] = (new BrowseColumn())
->setField('fin.trs.head.curcode')
->setLabel('Currency')
->setVisible(true);
$columns[] = (new BrowseColumn())
->setField('fin.trs.line.valuesigned')
->setLabel('Value')
->setVisible(true);
$columns[] = (new BrowseColumn())
->setField('fin.trs.line.description')
->setLabel('Description')
->setVisible(true);
// Second, create sort fields
$sortFields[] = new BrowseSortField('fin.trs.head.code');
// Get the browse data
$browseData = $connector->getBrowseData('000', $columns, $sortFields);
The ApiConnector has a constructor second parameter that can be used to configure some aspects of its operation.
The ApiOptions has the following methods signature:
/**
* This will allow you to enfornce the messages or the number of max retries.
* Passing null you will use the default values.
*/
public function __construct(?array $messages = null, ?int $maxRetries = null);
/**
* This will allow you to get all the exception messages
*/
public function getRetriableExceptionMessages(): array
/**
* This will allow you to replace the exception messages that should be retried
*/
public function setRetriableExceptionMessages(array $retriableExceptionMessages): ApiOptions
/**
* This will allow you to add new messages to the array of exception messages
*/
public function addMessages(array $messages): ApiOptions
/**
* This will allow you to get the number of max retries
*/
public function getMaxRetries(): int
/**
* This will allow you to set the number of max retries
*/
public function setMaxRetries(int $maxRetries): ApiOptions
❗ All the get methods will return a new instance with the configuration you changed.
Below are some examples on how to use the configuration object
$connector = new BrowseDataApiConnector(
$connection,
new ApiOptions(
[
"SSL: Connection reset by peer",
"Bad Gateway"
],
3
)
);
The example below will look for the default messages plus the "Bad Gateway" message.
$options = new ApiOptions(
null,
3
);
$connector = new BrowseDataApiConnector(
$connection,
$options->addMessages(["Bad Gateway"])
);
Attribute | Default Value | Description |
---|---|---|
Max retries | 3 | The number of retries that should happen before throwing an error. |
Retriable exception messages | [ "SSL: Connection reset by peer", "Your logon credentials are not valid anymore. Try to log on again." ] |
The exception messages that should be match in order to retry automatically. |
Not all resources from the Twinfield API are currently implemented. Feel free to create a pull request when you need support for another resource.
Component | get() | listAll() | send() | delete() | Mapper |
---|---|---|---|---|---|
Articles | ✅ | ✅ | ✅ | ||
BankTransaction | ✅ | ✅ | |||
Customer | ✅ | ✅ | ✅ | ✅ | |
Electronic Bank Statements | ✅ | ✅ | ⛔ | ||
Sales Invoices | ✅ | ✅ | ✅ | ||
Matching | ✅ | ✅ | |||
Offices | ✅ | ✅ | |||
Suppliers | ✅ | ✅ | ✅ | ✅ | |
Transactions: Purchase, Sale, Journal, Cash |
✅ | ✅ | ✅ | ✅ | |
Users | ✅ | ||||
Vat types | ✅ | ||||
Browse Data | ✅ | ✅ |
⛔ : Not supported by the Twinfield API