I have the email warning of the end of the legacy API
I am not computer minded and most of the wording is gibberish to me
Will there be clearer instructions on managing this or is it time to find a new app?
I have the email warning of the end of the legacy API
I am not computer minded and most of the wording is gibberish to me
Will there be clearer instructions on managing this or is it time to find a new app?
Hi @rossdunbar
How have you used the API up until now? Is this something you have done, or did you hire a developer to do it for you?
I have various integrations all using XML via excel, will I still be able to use XML?
Hi @Rob
The XML API will also be depreciated next year.
You may be able to upgrade it to the newer API, we’ve ensured that everything you could do in the older API is available in the new version, it’s just JSON rather than XML and requires a different type of authentication.
Just so I understand, it is just the authentication method that will need to change? can i leave everything as is apart from sending over to quickfile via api?
The new API is JSON rather than XML (different formatting).
For example, to create a bank transaction using the current API, you would do something like this (using XML):
<Bank_CreateTransaction xmlns="https://api.quickfile.co.uk" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://api.quickfile.co.uk https://api.quickfile.co.uk/schemas/1_2/Bank_CreateTransaction.xsd">
<Header>
<MessageType>Request</MessageType>
<SubmissionNumber>00000001</SubmissionNumber>
<Authentication>
<AccNumber>123456</AccNumber>
<MD5Value>7dd259dea3393880406d292e3f6f5830</MD5Value>
<ApplicationID>appID</ApplicationID>
</Authentication>
</Header>
<Body>
<Transaction>
<BankNominalCode>1200</BankNominalCode>
<Date>2017-03-13</Date>
<Reference>My test bank entry</Reference>
<Notes>transaction notes..</Notes>
<Amount>35.65</Amount>
</Transaction>
<DuplicateFilterOn>true</DuplicateFilterOn>
</Body>
</Bank_CreateTransaction>
This also includes the “authentication” header information.
The new API would be like this:
{
"date": "2026-09-01",
"reference": "My test bank entry",
"notes": "transaction notes..",
"amount": 35.65,
"duplicate_check": true
}
The authentication for the new one would be as a header field:
Authorization: Bearer {Your token here}
Here’s the documentation for reference: