Hi Joewie,<br>Thank you for the feedback and for sharing the comments from the evaluation<br>committee.<br>While we are happy to provide additional details regarding our solution and<br>process flow, I must express our deep disappointment regarding the<br>engagement so far.<br>Despite our genuine efforts and numerous attempts to progress<br>collaboratively, it has become evident that there was never any real<br>intention to provide us with the required API access. This has<br>unfortunately resulted in a significant loss of valuable time and resources<br>on our end, which could have been avoided with clearer communication from<br>the outset.<br>At this stage, we would like to clarify that we will not be proceeding with<br>the use of your API. It has become clear to us that there was no genuine<br>intention to provide us with the necessary access or support from the<br>beginning. This has resulted in an unnecessary loss of time and resources<br>on our part.<br>Moving forward, we are choosing to partner with more transparent and<br>collaborative organizations that share our commitment to clarity and mutual<br>respect from the outset.<br>We are extremely dissapointed with the frustration and  interaction thus<br>far and wish better experience in the future endeavors with other clients<br>who seek the same.<br>Regards,<br>Kevin Amayi.<br>On Thu, Apr 10, 2025 at 2:26 PM ZA - SL - Pastel - MB - My Business - API <<br>api@accounting.sageone.co.za> wrote:<br>> Hi David,<br>><br>><br>><br>> Kindly see the comments from the evaluation committee below.<br>><br>><br>><br>> Please provide a much-detailed process flow of your solution, to clarify<br>> the frequency of syncing the data.<br>><br>><br>><br>> Additionally, please advise if you have considered and or implemented the<br>> use of OData filters, e.g. filtering by Modified date to check for updates.<br>><br>><br>><br>> If not, please find the attached document titled, “OData Filters” which<br>> will guide you in using these.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Wednesday, 09 April 2025 14:47<br>> *To:* ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za><br>> *Cc:* Kubushi, Joewie ; KEVIN AMAYI <<br>> kevinamayi20@gmail.com>; info@tagrit.com; Capabuil Ltd ;<br>> Reagan Nyadimo ; nafisa.ahmed@capabuil.com<br>> *Subject:* Re: Still Following up on the Live API<br>><br>><br>><br>> *EXTERNAL EMAIL*<br>><br>> Good Afternoon,<br>><br>><br>><br>> Could you please provide us with an update and the  status of this Request<br>> ?<br>><br>><br>><br>> On Thu, Apr 3, 2025 at 4:28 PM ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za> wrote:<br>><br>> Hi David,<br>><br>><br>><br>> Kindly note that your response is well received and will be shared with<br>> the evaluation committee.<br>><br>><br>><br>> Please note that we will provide any updates from the committee, once<br>> available.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Thursday, 03 April 2025 15:10<br>> *To:* Kubushi, Joewie <br>> *Cc:* ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za>; KEVIN AMAYI ;<br>> info@tagrit.com; Capabuil Ltd ; Reagan Nyadimo <<br>> reagan.nyadimo@capabuil.com>; nafisa.ahmed@capabuil.com<br>> *Subject:* Re: Still Following up on the Live API<br>><br>><br>><br>> *EXTERNAL EMAIL*<br>><br>> Dear Joewie and Sage API Team,<br>><br>>  Good morning,<br>><br>>  Thank you for your previous clarification regarding the daily frequency<br>> requirements for each API endpoint. Based on the information provided in<br>> Section 12 of your Developer Services License Agreement, as well as the<br>> list of endpoints we will be using, we have revised our estimated daily API<br>> call frequencies to ensure compliance with your usage limits while<br>> accounting for the synchronization of historical data from 2018 to the<br>> present.<br>><br>>  Our system is designed to perform automatic synchronization every 30<br>> minutes , ensuring near real-time updates between Sage and our third-party<br>> system. To comply with your 2,500 daily API calls per company and 100 calls<br>> per minute limits, we have implemented the following strategies:<br>><br>>  Revised API Endpoints and Daily Call Frequencies<br>><br>> Below is the updated breakdown of our estimated API call frequencies,<br>> ensuring full compliance with Sage's policies:<br>><br>><br>><br>> *ENDPOINT DAILY CALLS*<br>><br>> Company/Get = 5<br>><br>> Customer/Get = 400<br>><br>> Customer/Save = 50<br>><br>> CustomerCategory/Get = 10<br>><br>> CustomerCategory/Save = 5<br>><br>> TaxInvoice/Get = 600<br>><br>> TaxInvoice/Save = 30<br>><br>> CustomerReceipt/Get = 200<br>><br>> CustomerReceipt/Save = 20<br>><br>> SupplierInvoice/Get = 400<br>><br>> SupplierInvoice/Save = 20<br>><br>> SupplierPayment/Save = 15<br>><br>> Allocation/Get = 100<br>><br>> Allocation/Save = 10<br>><br>> Item/Get = 400<br>><br>> Item/Save = 30<br>><br>> ItemCategory/Get = 10<br>><br>> ItemCategory/Save = 5<br>><br>> BankAccount/Get = 10<br>><br>> Supplier/Get = 200<br>><br>> Supplier/Save = 20<br>><br>><br>><br>> *Compliance with Usage Limits*<br>><br>> *Automatic Sync Every 30 Minutes:*<br>><br>> Our system performs synchronization every *30 minutes* , resulting in *48<br>> sync* cycles per day .<br>><br>> To ensure compliance with the *2,500 daily limit* , we have distributed<br>> API calls across high-priority endpoints (e.g., Customer/Get,<br>> TaxInvoice/Get, SupplierInvoice/Get) and minimized calls to low-priority<br>> endpoints (e.g., Company/Get, BankAccount/Get).<br>><br>><br>><br>> *Pagination and Date Range Filtering:*<br>><br>> High-volume endpoints like TaxInvoice/Get and Customer/Get will retrieve<br>> data in paginated batches or filtered date ranges during each sync cycle.<br>> For example:<br>><br>> Instead of retrieving all invoices in a single call, we will fetch<br>> invoices in smaller chunks (e.g., monthly or quarterly intervals).<br>><br>> This approach ensures that no single sync cycle exceeds the allowed number<br>> of calls.<br>><br>><br>><br>> * Rate-Limiting Compliance:*<br>><br>> To avoid exceeding the *100 calls per minute* threshold:<br>><br>> API calls will be staggered across the 30-minute interval to ensure no<br>> more than 1–2 calls per second .<br>><br>> Resource-intensive endpoints (e.g., Allocation/Get, TaxInvoice/Get) will<br>> be scheduled during off-peak hours to minimize performance impact.<br>><br>> *Total Daily Calls:*<br>><br>> The above estimates result in a total of 2,495 API calls per day , leaving<br>> a small buffer to account for any unexpected spikes or adjustments.<br>><br>><br>><br>> *Additional Notes:*<br>><br>> *High-Volume Endpoints:*<br>><br>> The highest-volume endpoints (Customer/Get, TaxInvoice/Get,<br>> SupplierInvoice/Get, Item/Get) have been allocated more calls to<br>> accommodate the synchronization of historical data from 2018 to the present.<br>><br>> *Manual Sync vs Automatic Sync:*<br>><br>> For manual sync operations, each endpoint will be called once per<br>> execution.<br>><br>> For automatic sync, the total daily calls are distributed across the 48<br>> sync cycles, ensuring compliance with Sage's rate limits.<br>><br>> *Future Adjustments:*<br>><br>> We will monitor API usage closely and adjust our integration to align with<br>> any future updates to your usage limits or policies.<br>><br>> We hope this revised breakdown provides the clarity you require to assess<br>> the impact of our solution. Please let us know if there are any further<br>> adjustments or clarifications needed.<br>><br>><br>><br>> Looking forward to your prompt response and the issuance of the Live API<br>> Key.<br>><br>><br>><br>><br>><br>><br>><br>><br>> --<br>><br>><br>><br>><br>><br>> *David Amukowa *<br>><br>> *IT Consultant *<br>><br>><br>><br>><br>>