Tony Fletcher

Hi @Ben Smith, are there any plans to update your Swagger file so it shows the correct responses the API returns (i.e. including the pagination elements)? It is 2 years on from this thread and this is still a problem that has not been resolved.

Thank you @Paul Millard, we have run into the same issue which we have emailed Sage about and your attachment has been very helpful. We have been dreading integrating with Sage after having previous experience with other Sage API's and so far it seems our fears have been justified, when compared to how easy it is to integrate with Xero, the integration with Sage is already causing problems and we have barely even started. We were adding a reference to Sage's swagger file to auto generate the code in Visual Studio for calling their API and as you have explained above the responses set out in their swagger file do not match what the API actually returns. I can see that you have updated the swagger file for "LedgerAccounts", "Products" and "BankAccounts" but I assume we will need to do the same for any API calls that are supposed to return an array of items or is it only those three that are affected by this issue? Hopefully Sage can update their swagger file so that it shows the correct responses that their API returns because we don't really want to have to keep manually modifying the swagger file each time they release a new version of their API.