Hi Joewie, I think the Information you keep on asking for  has already been<br>shared with you  by Kevin .<br>Does this Answer what you are Looking for ?<br>Dear Joewie,<br>Thank you for your email and for outlining the API usage limits in Section<br>12 of the Developer Services License Agreement. We appreciate the clarity<br>on these standards and are committed to ensuring full compliance with<br>Sage’s API policies.<br>Based on the specified limitations, we have reviewed our request strategy<br>and will make the following adjustments to remain within the allowed<br>thresholds:<br>   -<br>   *Daily Request Limit (Section 12.4.2):* Our system will ensure that the<br>   total number of API requests does not exceed 2,500 per day per company,<br>   even though enforcement of this limit is not currently in place.<br>   -<br>   *Per-Minute Request Limit (Section 12.4.1):* We will maintain a request<br>   frequency of no more than one request per second to avoid surpassing the<br>   limit of 100 requests per minute. This will also prevent any risk of<br>   receiving an HTTP 429 error and a temporary one-hour IP block.<br>   -<br>   *Resource-Intensive API Calls (Section 12.4.5):* We will minimize the<br>   use of API calls that have a high impact on system performance.<br>   -<br>   *Fair Usage and System Performance Considerations (Sections 12.4.3 &<br>   12.4.4):* We recognize that Sage Accounting is optimized for small<br>   business usage, and we will ensure that our API interactions remain within<br>   the reasonable operational limits of 3,000 customers, 3,000 suppliers,<br>   5,000 items, 1,000 customer invoices, 1,000 supplier invoices, and 2,000<br>   bank transactions per month to prevent any adverse effects on reporting and<br>   overall system performance.<br>   -<br>   *Future Adjustments (Section 12.4.6):* We will monitor any updates to<br>   Sage’s API limits and adjust our integration accordingly to maintain<br>   compliance with any revised thresholds or enforcement mechanisms.<br>Please let us know if you have any additional recommendations or<br>requirements that we should consider. We appreciate your guidance in<br>ensuring seamless API integration.<br>That said, we kindly request that this issue be resolved as urgently as<br>possible to avoid disruptions that could slow down operations and frustrate<br>our processes. A swift resolution would be highly appreciated to maintain a<br>smooth experience for all stakeholders.<br>Looking forward to your prompt response.<br>Best regards,<br>*Kevin Amayi Musungu.*<br>*Chief Technology Officer (CTO)*<br>On Wed, Apr 2, 2025 at 10:58 AM Kubushi, Joewie <<br>JoewieHarvey.Kubushi@sage.com> wrote:<br>> Hi David,<br>><br>><br>><br>> Kindly note that we have sent out communication with a request from the<br>> evaluation team.<br>><br>> To avoid miscommunication, please confirm the contact person for all<br>> updates concerning the request to integrate with SBCA.<br>><br>> Please action the email attached and provide us with the information<br>> requested.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Wednesday, 02 April 2025 09:53<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>> Dear Sage API Team,<br>><br>> Good morning,<br>><br>><br>><br>> I am following up to inquire about the status of our request for the Live<br>> API Key , which we have been awaiting for nearly two months now. Despite<br>> multiple communications and providing all required information, we have yet<br>> to receive any updates or resolution on this matter.<br>><br>> Could you kindly provide us with an update on the progress and a clear<br>> timeline for when we can expect the Live API Key to be issued?<br>><br>> Your prompt response would be greatly appreciated.<br>><br>><br>><br>> On Tue, Apr 1, 2025 at 1:05 PM Prof David Amukowa <br>> wrote:<br>><br>> Dear Sage API Team,<br>><br>><br>><br>> Good Afternoon,<br>><br>><br>><br>> I hope this email finds you well. Unfortunately, I must express our<br>> growing frustration and dissatisfaction with the way this matter has been<br>> handled over the past two months. We have been patiently waiting for the<br>> issuance of the Live API Key, which is critical for us to proceed with<br>> integrating our systems. However, your team’s continued delays and<br>> repetitive requests for information that we have already provided are<br>> causing significant disruptions to our operations.<br>><br>><br>><br>> *To summarize:*<br>><br>><br>><br>> We initially requested the Live API Key nearly *two months ago.*<br>><br>> Since then, we have responded promptly and comprehensively to every<br>> request for clarification or additional details, including providing a<br>> detailed frequency plan adhering to the usage limits outlined in your<br>> Developer Services License Agreement.<br>><br>> Despite this, your team continues to rotate the same questions back to us,<br>> delaying progress unnecessarily.<br>><br>><br>><br>> *The impact of this delay is severe:*<br>><br>><br>><br>> *Our imprest system integration* —which was scheduled to go live months<br>> ago—remains non-functional, leaving our accounting department overwhelmed<br>> with manual work.<br>><br>> Our staff are unable to automate critical processes such as imprest<br>> reconciliation, expense management, and data synchronization, leading to<br>> inefficiencies and errors.<br>><br>> The pile-up of unresolved tasks is affecting our overall productivity and<br>> timeline.<br>><br>> We fail to understand why this process has dragged on for so long. If<br>> there are concerns about our responses, why not take the initiative to<br>> issue the Live API Key with a default limit configured on your side? For<br>> example, you could impose a reasonable cap on API calls per day or minute<br>> (as per your own guidelines) and inform us accordingly. This would allow us<br>> to move forward while ensuring compliance with your policies.<br>><br>><br>><br>> Instead, your team keeps rotating the same questions, wasting valuable<br>> time and frustrating us as clients. *Since Capabuil Limited As a loyal<br>> customer since 2019, we expected better professionalism and responsiveness<br>> from Sage.*<br>><br>><br>><br>> If your intention is not to provide us with the Live API Key, we would<br>> appreciate it if you informed us outright so that we can explore<br>> alternative solutions. However, keeping us in limbo for two months is<br>> neither professional nor acceptable.<br>><br>><br>><br>> *To reiterate, here’s what we need:*<br>><br>><br>><br>> Immediate issuance of the *Live API Key ,* even with default limits<br>> imposed by your team.<br>><br>> Clear communication on any outstanding requirements or concerns so that we<br>> can address them promptly.<br>><br>> We urge you to treat this matter with the urgency it deserves. Please<br>> respond within the next 24 hours with a concrete resolution or timeline.<br>><br>><br>><br>> Thank you for your attention to this matter.<br>><br>><br>><br>><br>> --<br>><br>><br>><br>><br>><br>> *David Amukowa *<br>><br>> *IT Consultant *<br>><br>><br>><br>><br>> [image: Sage]<br>><br>> The information contained in this email transmission may constitute<br>> confidential information. If you are not the intended recipient, please<br>> take notice that reuse of the information is prohibited.<br>><br>><br>-- <br>*David Amukowa *<br>*IT Consultant *