Steel, Mark

Hi Rajni, I'm not sure that Sage 50 Accounting Cloud API is something that is supported and shouldn't be confused with the Sage 50 product SDK's. For further information relating to the product SDK's you can reach out to [email protected]. Thanks Mark

Hi Andrew, The API's are at present, free to use.

Hi Andrew We have two tickets in our backlog to complete the Analysis Types API exposure. SBS-48029 - To expose analysis type transactions. Use case - Integrating application has a requirement to obtain historic and realtime data for analysis types. At present it's not possible to identify from transactions or the originating artefact type if analysis types have been defined. The only method of obtaining this information is to iterate every transaction which potentially has analysis types defined. This is hugely inefficient and has the potential to place a large strain on server resources. SBS-48032 - To expose the group analysis on customers, suppliers, products, stock_items and service_items. Use case - An integrating application needs to associate a contact with a new analysis_type_category they've created for GROUP analysis types. The implementation of SBS-48029 will provide an indicator that can be used to identify invoices with analysis type data in the index request as you require. Due to the architecture of the analysis types data and the relationship to artefacts it is unlikely that we'd be able to provide the analysis_type data in such a request due to its efficiency. The request you provided above would potentially cause a 504 timeout if there were a few invoices with many item lines.

Hi Rich - Thank you for your post. If you know the Sage Product or products you require the expertise for, you could try looking at the Sage Marketplace which lists integrators by product. It may be that contacting the integrators listed provides you with greater choice. Thanks Mark Steel

Hi Mohammed, Active is only ever true or false and status values are trial, paying and expired. To answer your question, if the status is expired you will not be able to access the accounts data either in the UI or via the API's. Thanks Mark

Hi, you're able to setup trial accounts to use for Dev purposes - https://developer.sage.com/accounting/quick-start/set-up-the-basics/

Hi Thanks for your question. SBCA will not allow you to add a discount amount/percentage to a line item if it causes a negative line item total. For example you enter a positive amount of 100 and then discount it by 200% to give a negative -100. What is the requirement here? Are you wanting to ensure the discount amount is correctly attributed to the discount nominal/ledger in the P&L? You'll also need to consider the tax_code you're using. Entering a negative item line will create a debit value for the tax liability. Should this transaction be reducing the tax_liability? Thanks Mark

Hi Stefan, You'll probably need to look for a free text field with a large character allowance. If the URL is related to a specific artefact such as a sales_invoice for example the notes field would be ideal for this. Thanks Mark

Thanks for clarifying, The list of Invoices is obtained using the sales_invoices API which will return the id, displayed_as(invoice_number) and path. Is there any other detail that you require to show in addition to the invoice_number in your sales_invoice list? For example you may wish to show the invoice_date and or the contact which can be requested by passing in the attributes parameter - sales_invoices?attributes=contact,date. The full details of the invoice are then obtained by passing the id to the sales_invoices API. I would recommend doing this as and when they require the details of the individual invoice rather than trying to sync all of their data. There's no public method available that would allow you to send an invoice to the customer. You would need to create the invoice and then use a GET request with the header parameter for accept set to application/pdf. This would provide you with a PDF which could then be sent to the customer using an email service of your choosing. Setting the sent attribute to true would only show the invoice as being sent in the UI. It would not invoke a method to send it to the contact. We don't have an SDK specific to asp.net, there is a .net core example in the sample code https://developer.sage.com/accounting/guides/getting-started/sample_apps/. If you're looking for guidance, I find the code examples offered in POSTMAN to provide great value and direction for specific coding languages. Thanks Mark

Hi Ahmad, At present the SDK support for Sage 50 sits with different teams depending on local. For SDK support with Sage 50 in North America you'll need to email [email protected]. Thanks Mark

Hi Stefan, The error is generally related to the parameters you are passing to create the contact for the business's associated tier. Sage Business Cloud Accounting is available in three tiers with varying functionality between the tiers. It looks as if you're trying to pass an attribute that is not available in the Accounting Tier or the registered_number you are passing is not a valid field for the UK. In this case it looks to be the latter which is the issue, the registered_number of the contact's business, is only used for German businesses and represents the "Steuernummer". It's an invalid field for any other region including the UK. Thanks Mark

https://api.accounting.sage.com/v3.1/sales_invoices is the index request which tells you the number of records available and provides you with the id's of the sales_invoices should you require the detail of the transaction. The path that is returned by the index https://api.accounting.sage.com/v3.1/sales_invoices/586117de375711e8b45c025132dab352 will return the sales invoice details for the requested id. What data do you require from the sales_invoice. If you can provide us with the scope of the integration and the requirements we will be able to suggest the most efficient ways of obtaining the data. Thanks Mark

What have you changed in the config of the C# sample app GitHub - Sage/sageone_api_csharp_sample: Sage One API - C# Sample?

Hi - this message is generally returned during the exchange of the auth_code for the tokens. It is usually because you have not correctly URL encoded the body params you're passing.

Hi Andrew Thanks for your question. Corrections are created when a Bank or Vat reconciled transaction is edited. For example, a customer_receipt allocated to a sales_invoice has been bank reconciled and then the reference of the customer_receipt modified. This would then create an entry in the corrections table of the db. The issue is that the transactions API does not currently see the corrections data and therefore is currently unable to provide an identifier to the transaction that allows it to be identified as corrected. The origin_id returned for the corrected transaction is held in the corrections data and therefore cannot be accessed by the API. I've replied to you on a separate email thread to work it through between us. In the meantime, the issue has been logged for consideration with an internal reference of AC-7764.

https://api.accounting.sage.com/v3.1/sales_invoices is the index request which tells you the number of records available and provides you with the id's of the sales_invoices should you require the detail of the transaction. The path that is returned by the index https://api.accounting.sage.com/v3.1/sales_invoices/586117de375711e8b45c025132dab352 will return the sales invoice details for the requested id. What data do you require from the sales_invoice. If you can provide us with the scope of the integration and the requirements we will be able to suggest the most efficient ways of obtaining the data. Thanks Mark

GET https://api.accounting.sage.com/v3.1/ledger_accounts?ledger_account_type_id=SALES { "$total": 6, "$page": 1, "$next": null, "$back": null, "$itemsPerPage": 20, "$items": [ { "id": "4af2ca6f2d1511edb2850279d0cc53c5", "displayed_as": "Sales - Contract Recrtuiment (4010)", "$path": "/ledger_accounts/4af2ca6f2d1511edb2850279d0cc53c5" }, { "id": "4af313f12d1511edb2850279d0cc53c5", "displayed_as": "Sales Discounts (4045)", "$path": "/ledger_accounts/4af313f12d1511edb2850279d0cc53c5" }, { "id": "4af3e5712d1511edb2850279d0cc53c5", "displayed_as": "Commissions Received (4070)", "$path": "/ledger_accounts/4af3e5712d1511edb2850279d0cc53c5" }, { "id": "4afa33f02d1511edb2850279d0cc53c5", "displayed_as": "Sales - Permanent Recruitment (4000)", "$path": "/ledger_accounts/4afa33f02d1511edb2850279d0cc53c5" }, { "id": "0cdb79874c3f441299a527ba63f73dca", "displayed_as": "Sales - Subscriptions (4030)", "$path": "/ledger_accounts/0cdb79874c3f441299a527ba63f73dca" }, { "id": "f60fb179481646f3882d29cb4635e61f", "displayed_as": "Sales - Recharges (4040)", "$path": "/ledger_accounts/f60fb179481646f3882d29cb4635e61f" } ] } It looks as if you've passed the incorrect query parameter you're using ledger_account_type_id and it needs to be ledger_accounts_type_id

The callback URL you've set doesn't look correct. If you're using the POSTMAN app try using the POSTMAN callbackurl - https://www.postman.com/oauth2/callback first before moving on to your localhost callback. You'll also need to add this to your app registry callback urls. I would also change the Client Authentication to Send as Basic Auth header. It looks as if the images we have in the docs are out of date and could do with updating. Thanks Mark

Can you send me the parameters that you send in the auth URl please. You'll need to hide your client_id and secret. The auth redirect should be taking you to the country selection if not set as a query param and then to the user auth grant attached.

The auth flow is the owner of a business granting access to your application. It is the business owners email address and password that is required and not your app credentials. The app credentials are known from the params passed in the auth request.

Thanks, That's not going to work. You need to auth against a business as per this guide.

Hi, what is the email address you are using to authenticate with please? Feel free to send it in a direct message if you don't wish to make it public. Thanks Mark

Hi, The Invoice Headers (date, invoice_number, due_date, reference, address, etc) do not need to be included in the PUT body. Adding all of the item lines is sufficient and the invoice totals will be re-calculated based on the values in the invoice_lines you include. Thanks

HI, Thank you for your question. You would need to send all item lines that you need to keep along with their associated values including any analysis_types that they may be associated with. If you sent only the invoice_line that you wish to add/change the invoice would then only have a single invoice_line. Have you created a trial account to develop against and test your code? Thanks Mark