In a nutshell:
In this article, you will find answers to the most frequently asked questions about our open programming interface, the Taxdoo API. Do you have a question that you haven't found the answer to in this article? Please feel free to send us a message through the help center.
What can I transmit / query with the Taxdoo API?
You can transmit and access data on orders, refunds, intra-community movements, products, and warehouses. In addition, information on your Taxdoo account, your VAT registrations stored with us and certain reports such as transaction lists and DATEV exports can be called up. The endpoints to be used in each case are described in detail in our documentation.
What is the minimum payload I have to send?
The scope of the data to be transmitted is listed in detail for all endpoints in our documentation.
Example: Add Transactions endpoint
A detailed description of the content to be transferred (payload) can be found if we click on the link listed under Type (here Transaction).
All fields in bold are mandatory, while fields not in bold are optional. Please also note the general description, which in this case indicates to what extent the fields paymentDate and sentDate have to be specified, although they are not printed in bold.
What do I have to pay particular attention to?
Please read the descriptions of the respective endpoints (e.g. Transactions) carefully, as there are some special features to consider, which includes:
- always transfers gross amounts for all monetary fields (e.g. itemPrice)
- For B2B transactions, the VAT ID of the buyer must be provided in the buyerVatNumber field
- make sure that the correct identifier is given for transactions that were processed via a marketplace (you can find the values here)
- enter negative values for refunds (e.g. itemPrice and shipping are negative, discount would be positive)
- there is no multiplication of the quantity with monetary fields such as itemPrice or shipping, so you have to enter the total value of the item in these fields
What is the difference between Transactions, Orders, and Refunds?
You can transmit sales and refunds completely via the Transactions endpoint, with one line always corresponding to a position in the order / refund. For orders with multiple items, we recommend using the Orders endpoint, as data such as the identifier or the transaction number only need to be specified once and are used for all order items.
The Refunds end point is the counterpart to the Orders end point, and you can use it to transfer refunds with multiple items.