Retrieves a list of articles. The articles are returned sorted by article number with the lowest number appearing first.

The created article will be returned if everything succeeded, if there was any problems an error will be returned.

This is a helper method to calculate the prices for all sub items in a bundle. Several bundles can be included in the same request, as separate rows, and be calculated at the same time.

Some properties are required for the price calculation to work:

• The bundle row (the top row) must have a Price. This is the price of the bundle, which the prices of the sub items will be calculated from. The goal of the calculation is to make the sum of the prices of the sub items equal to this price.
• Each sub item row must have an AmountInBundle and a SalesPriceInBundle. These values are necessary in order to determine how large part of the bundle's value the sub item represents, and what the price of the sub item must be.
• If a sub item row has UserPrice set to true, the Price property must also be set. The Price property of the sub items is normally not used as input, but if the UserPrice flag is set, the provided Price will be used as the price of the sub item and not calculated. This works in the same way as if a sub item had a fixed price in the bundle.

This method can also (optionally) calculate the price of the price adjustment row of a bundle. To have the price adjustment row price calculated, an additional sub row having the PriceAdjustment property set to true must be included in the request. If a price adjustment row is provided, in order for its price to be calculated, the following properties must be set (in addition to the properties specified above):

• The Quantity on all rows, the bundle row and the sub rows.
• The Discount on the bundle row (if the bundle should be sold with a discount).

This method will only calculate the prices of the sub rows and return these prices in the response. No modifications will be made to any entities in the database.

Example: To add a bundle to an invoice, first get the bundle article from the article registry. Here you will find the sub items included in the bundle, and how many of each there are in a bundle.

GET /3/articles-v2/toolbox

Response (simplified):

 {
     "Article": {
     .
     .
     "Bundle": {
             "Comment": "",
             "PriceAdjustmentRow": {
                 .
                 .
             },
             "SubItems": [
                 {
                     "ArticleNumber": "hammer",
                     "Quantity": "2",
                     "FixedPrice": false
                 },
                 {
                     "ArticleNumber": "wrench",
                     "Quantity": "3",
                     "FixedPrice": false
                 }
             ]
         }
     }
 }
 

Then lookup the sales price for each of the included articles in the price list you intend to use on the invoice. This should always be the sales price for 1 unit of the article, if an article has more than one price, choose the price where "FromQuantity" is equal to 1 or the closest value below 1.

GET /3/prices/sublist/A/hammer

Response (simplified):

 {
     "Prices": [
          {
              "ArticleNumber": "hammer",
              "FromQuantity": 0,
              "PriceList": "A",
              "Price": 200
          }
     ]
 }
 

GET /3/prices/sublist/A/wrench

Response (simplified):

 {
     "Prices": [
          {
              "ArticleNumber": "wrench",
              "FromQuantity": 0,
              "PriceList": "A",
              "Price": 300
          }
     ]
 }
 

Now we have all the information we need to calculate the prices for the bundle. Let's assume that we want to sell this bundle for 1100 SEK, and that the customer bought 2 bundles. We also want the price adjustment to be calculated. We create a bundle price calculation request with the following properties:

 {
     "BundlePriceCalculation": {
         "Rows": [
             {
                 "Price": 1100,    // The price we want to set on the bundle
                 "Quantity": 2,   // The number of bundles sold (only required since we want to calculate the price adjustment row)
                 "Bundle": {
                     "SubRows": [
                         {
                             "Quantity": 4, // The number of hammers on the invoice. The bundle contains 2, but we sold 2 bundles.
                             "BundleSubItem": {
                                 "AmountInBundle": 2, // The amount of hammers in a bundle
                                 "SalesPriceInBundle": 200 // The sales price of the hammer
                             }
                         },
                         {
                             "Quantity": 6,
                             "BundleSubItem": {
                                 "AmountInBundle": 3,
                                 "SalesPriceInBundle": 300
                             }
                         },
                         {
                             "Quantity": 1,
                             "BundleSubItem": {
                                 "PriceAdjustment": true
                             }
                         }
                     ]
                 }
             }
         ]
     }
 }
 

We do the calculation by calling the endpoint with the request above:

POST /3/articles-v2/calculatebundleprices

Response (simplified):

 {
     "BundlePriceCalculation": {
         "Rows": [
             {
                 "Price": 1100,
                 "Quantity": 2,
                 "Bundle": {
                     "SubRows": [
                         {
                             "Price": 169.23,  // The price that the hammer should have on the invoice
                             "Quantity": 4,
                             "BundleSubItem": {
                                 "AmountInBundle": 2,
                                 "SalesPriceInBundle": 200
                             }
                         },
                         {
                             "Price": 253.85, // The price that the wrench should have on the invoice
                             "Quantity": 6,
                             "BundleSubItem": {
                                 "AmountInBundle": 3,
                                 "SalesPriceInBundle": 300
                             }
                         },
                         {
                             "Price": -0.02,  // The price to set on the price adjustment row
                             "Quantity": 1,   // Quantity is always 1 on a price adjustment row
                             "BundleSubItem": {
                                 "AmountInBundle": 0,
                                 "PriceAdjustment": true,
                                 "SalesPriceInBundle": 0
                             }
                         }
                     ]
                 }
             }
         ]
     }
 }
 

And there we have it. When we create our invoice, the price of the hammer should be set to 169.23 SEK, the price of the wrench must be set to 253.85 SEK, and the price adjustment row must be set to -0.02 SEK. The closest we could get to the desired price of 1100 SEK was 1100.01 SEK (2 * 169.23 + 3 * 253.85 = 1100.01 SEK), so the price for one bundle needed to be adjusted by -0.01 SEK. Since we calculated the price for 2 bundles, the total adjustment was -0.02 SEK.

Worth noting is that the prices for the articles in a bundle is always calculated based on exactly 1.0 bundle, the prices of the articles is not effected by the number of bundles sold. However, as seen in this example, the price adjustment might be. The same goes for discount. If a bundle is sold with a discount, the discount will not affect the calculated prices of the individual sub articles in the bundle, but it might affect the price on the price adjustment row.

Deletes the article permanently.

You need to supply the unique article number that was returned when the article was created or retrieved from the list of articles.

Retrieves the details of an article. You need to supply the unique article number that was returned when the article was created or retrieved from the list of articles.

Updates the specified article with the values provided in the properties. Any property not provided will be left unchanged. You need to supply the unique article number that was returned when the article was created or retrieved from the list of articles. Note that even though the article number is writeable you can not change the number of an existing article.

An endpoint for creating an invoice. While it is possible to create an invoice without rows, we encourage you to add them if you can. Omitted values in the payload will be supplied by Predefined values which can be edited in the Fortnox account settings. Note that Predefined values will always be overwritten by values provided through the API.

Should you have EasyVat enabled, it is mandatory to provide an account in the request should you use a custom VAT rate.

This endpoint can produce errors, some of which may only be relevant for EasyVat. Refer to the table below.

Note: The EuQuarterlyReport property will become obsolete at 2021-12-01. This property is currently used by the Quarterly report as one of the conditions that determine if an invoice should be included in the report or not. A new version of the Quarterly report is released at 2021-12-01. In the new report, this property will not be used when determining if an invoice should be included in the report or not, with one exception: if the invoice is created before 2021-12-01, and this property is false, the invoice will be excluded from the report. For invoices created 2021-12-01 and later, this property will have no effect.

Note that there are two approaches for updating the rows on an invoice.

If RowId is not specified on any row, the rows will be mapped and updated in the order in which they are set in the array. All rows that should remain on the invoice needs to be provided.

If RowId is specified on one or more rows the following goes: Corresponding row with that id will be updated. The rows without RowId will be interpreted as new rows. If a row should not be updated but remain on the invoice then specify only RowId like { "RowId": 123 }, otherwise it will be removed. Note that new RowIds are generated for all rows every time an invoice is updated.

Note: The EuQuarterlyReport property will become obsolete at 2021-12-01. This property is currently used by the Quarterly report as one of the conditions that determine if an invoice should be included in the report or not. A new version of the Quarterly report is released at 2021-12-01. In the new report, this property will not be used when determining if an invoice should be included in the report or not, with one exception: if the invoice is created before 2021-12-01, and this property is false, the invoice will be excluded from the report. For invoices created 2021-12-01 and later, this property will have no effect.

The created credit invoice will be referenced in the property CreditInvoiceReference.