Good morning Joewie,<br>I hope this email finds you well.<br>We are pleased to inform you that we have completed testing the Sandbox<br>API, and everything appears to be functioning as expected. With the testing<br>phase successfully concluded, we are now ready to move forward with the<br>integration into our production environment.<br>To facilitate this, we kindly request the issuance of the Live API Key so<br>that we can proceed with using the API in our live system. This integration<br>is critical as we have a third-party system currently being used by our<br>staff for imprest and expense management. Once the reconciliation process<br>for imprest is completed, the system needs to automatically post the data<br>to our Sage system, and the Live API Key will enable us to achieve this<br>seamlessly.<br>For reference, below is the Sandbox API information that was provided to us<br>two weeks ago:<br>------------------------------<br>Sandbox API Details:<br>   - API URL: https://resellers.accounting.sageone.co.za/api/2.0.0<br>   - Sandbox API Key: {C2EF3A03-01E5-4830-9B2E-8391627F89CA}<br>   - Documentation & Samples: Sage Developer API Documentation<br />   - Support Group: Sage One API Google Group<br />   - Contact Email: api@accounting.sageone.co.za<br>------------------------------<br>As outlined in the initial communication, once development and testing in<br>the Sandbox environment are complete, the next step is to request the Live<br>API Key and corresponding URL. We have fulfilled this requirement and are<br>now seeking your assistance to provide the necessary credentials for the<br>production environment.<br>Please let us know if there are any additional steps or documentation<br>required from our side to expedite this process. We appreciate your support<br>and look forward to receiving the Live API Key at your earliest convenience.<br>Thank you for your assistance, and we remain available should you need any<br>further clarification.<br>On Fri, Feb 21, 2025 at 1:19 PM Kubushi, Joewie <<br>JoewieHarvey.Kubushi@sage.com> wrote:<br>> Hi David,<br>><br>><br>><br>> You can create a test company by visiting<br>> https://resellers.accounting.sageone.co.za and signing up for the 30-day<br>> trial, we can extend the expiry of this company to fit your expected<br>> development window if necessary and all we would need is the email address<br>> used to register the company.<br>><br>> When you are ready to begin, use the following URL for the API:<br>> https://resellers.accounting.sageone.co.za/api/2.0.0.<br>> We use basic auth for authentication API calls and you would use the same<br>> login that you created in the step above.<br>><br>> Your API key for the Sandbox environment is:<br>> {C2EF3A03-01E5-4830-9B2E-8391627F89CA}<br>><br>> You can find the latest documentation as well as samples at the following<br>> URL:<br>> https://www.sage.com/en-za/sage-business-cloud/accounting/developer-api/.<br>><br>> In addition to the documentation please feel free to join our Google Group<br>> (https://groups.google.com/forum/#!forum/sageoneapi_southafrica) where<br>> you can find topics created by both the Sage One Accounting API Developers<br>> and Sage One Accounting 3rd party developers.<br>> Once you are a member of the group, you can post any queries or if you<br>> require any additional information on the API.<br>><br>> Please feel free to contact us on api@accounting.sageone.co.za for any<br>> API related queries.<br>><br>> Once you have completed your development against this environment please<br>> inform us that you are ready to go live. We will then evaluate the calls<br>> made using the API key above for approval. If approved, we will issue a new<br>> API key for LIVE along with the corresponding URL.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Friday, 21 February 2025 12:04<br>> *To:* Kubushi, Joewie <br>> *Cc:* ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za>; KEVIN AMAYI ;<br>> hamiskf@gmail.com; simon mwachi ;<br>> ayoobet22@gmail.com; info@tagrit.com; My Angel My Everything <<br>> viviannamvuya@gmail.com><br>> *Subject:* Re: Request for API Key<br>><br>><br>><br>> *EXTERNAL EMAIL*<br>><br>> Good Afternoon sorry i think i picked the wrong   Partner Entity Company<br>> Number<br>><br>> I have amended the form with the Correct  Partner Entity Company Number .<br>><br>><br>><br>> On Fri, Feb 21, 2025 at 12:37 PM Prof David Amukowa <br>> wrote:<br>><br>><br>><br>> Dear Joewie and Sage Accounting API Team,<br>><br>><br>><br>> Please find attached the amended Form for your review<br>><br>><br>><br>><br>><br>><br>><br>> On Fri, Feb 21, 2025 at 12:18 PM Kubushi, Joewie <<br>> JoewieHarvey.Kubushi@sage.com> wrote:<br>><br>> Hi David,<br>><br>><br>><br>> Kindly see the answers to your queries below.<br>><br>><br>><br>>    1. Confirm which login URL we should use for API integration in Kenya<br>>    – *All integrations use the https://accounting.sageone.co.za/api/2.0.0<br>>    *<br>>    2. Provide country-specific documentation (especially for Kenya) to<br>>    guide our integration – *Please note that no country specific<br>>    documentation exists.*<br>>    3. Clarify the Partner Entity Company Number format applicable to<br>>    Kenya – *Please note that you can find this on your certificate of<br>>    registration in the native Kenyan format.*<br>>    4. Explain why we were asked to create another account via a different<br>>    link – *Please note that the https://accounting.sageone.co.za<br>>     was introduced to create a centralised<br>>    platform, on the login page you can select the country of origin, making it<br>>    easier to add an account or use Add-Ons.*<br>>    5. Simplify the process—having multiple links is frustrating and a bad<br>>    user experience.<br>><br>><br>>    1. *Please note that in order to proceed with the integration, you<br>>       will need to submit a completed and signed enrolment form, then we will<br>>       issue a Sandbox API Key which you will use to develop and test your<br>>       integration. *<br>>       2. *Once you have completed your integration, we will send a<br>>       questionnaire which will assist in the evaluation of your solution to be<br>>       granted a Live API Key.*<br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Friday, 21 February 2025 11:05<br>> *To:* Kubushi, Joewie <br>> *Cc:* ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za>; KEVIN AMAYI ;<br>> hamiskf@gmail.com; simon mwachi ;<br>> ayoobet22@gmail.com; info@tagrit.com; My Angel My Everything <<br>> viviannamvuya@gmail.com><br>> *Subject:* Re: Request for API Key<br>><br>><br>><br>> *EXTERNAL EMAIL*<br>><br>><br>><br>><br>><br>> Dear Joewie and Sage Accounting API Team,<br>><br>> I hope you are doing well.<br>><br>> We have been using Sage Accounting for almost four years now, and our main<br>> login has always been through this link:<br>><br>> ? *Login URL:* https://ke.accounting.sageone.co.za/<br>> ? *Email:* Tabithabarasa@capabuil.com<br>> ? *Password:* CB.sage@2023<br>><br>> However, we were recently provided with another link to create a new<br>> account:<br>><br>> ? *New Link:* https://accounting.sageone.co.za/Landing/Default.aspx<br>> ? *Same Email:* Tabithabarasa@capabuil.com<br>> ? *Same Password:* CB.sage@2023<br>><br>> This has caused a lot of confusion for us because we need to integrate<br>> Sage Accounting APIs with our internal system.<br>> *Our Key Requirement:*<br>><br>> We have a *third-party system* used by our staff to request *Imprest /<br>> Expense approvals*, and we want this system to communicate directly with *Sage<br>> Kenya* (i.e., https://ke.accounting.sageone.co.za/) to post approved<br>> expenses.<br>> *Our Concerns:*<br>><br>> 1.       *Too Many Links, No Clear Documentation:*<br>><br>> o   We do not understand why we have multiple login URLs.<br>><br>> o   Is https://ke.accounting.sageone.co.za/ specifically for Kenya?<br>><br>> o   What is the difference between this and<br>> https://accounting.sageone.co.za/?<br>><br>> o   Which URL should we use for API integration?<br>><br>> 2.       *Lack of Country-Specific Documentation:*<br>><br>> o   We need clear API documentation that applies to *Sage Kenya* and not<br>> a generic guide meant for South Africa.<br>><br>> o   Your API documentation should clearly define *what link to use per<br>> country* and how to integrate with it.<br>><br>> o   The response we received about the *Partner Entity Company Number* was<br>> also unclear. Why not provide documentation for different regions instead<br>> of using a South African format that does not apply to us?<br>><br>> 3.       *Frustrating and Unclear Process:*<br>><br>> o   The multiple steps, different links, and unclear guidance make the<br>> integration process unnecessarily complex.<br>><br>> o   We have already submitted an API key request, but we are still<br>> struggling with basic clarity on *which system instance we should<br>> integrate with.*<br>> *What We Need From You:*<br>><br>> 1.       Confirm *which login URL* we should use for *API integration* in<br>> Kenya.<br>><br>> 2.       Provide *country-specific documentation* (especially for Kenya)<br>> to guide our integration.<br>><br>> 3.       Clarify the *Partner Entity Company Number format* applicable to<br>> Kenya.<br>><br>> 4.       Explain why we were asked to create another account via a<br>> different link.<br>><br>> 5.       Simplify the process—having multiple links is frustrating and a<br>> bad user experience.<br>><br>> We appreciate your urgent feedback because this confusion is delaying our<br>> project. Kindly provide clear and precise responses so we can move forward<br>> without unnecessary back-and-forth emails.<br>><br>> Looking forward to your response.<br>><br>><br>><br>> On Fri, Feb 21, 2025 at 11:56 AM Prof David Amukowa <br>> wrote:<br>><br>> Dear Joewie and Sage Accounting API Team,<br>><br>> I hope you are doing well.<br>><br>> We have been using Sage Accounting for almost four years now, and our main<br>> login has always been through this link:<br>><br>> ? *Login URL:* https://ke.accounting.sageone.co.za/<br>> ? *Email:* Tabithabarasa@capabuil.com<br>> ? *Password:* CB.sage@2023<br>><br>> However, we were recently provided with another link to create a new<br>> account:<br>><br>> ? *New Link:* https://accounting.sageone.co.za/Landing/Default.aspx<br>> ? *Same Email:* Tabithabarasa@capabuil.com<br>> ? *Same Password:* CB.sage@2023<br>><br>> This has caused a lot of confusion for us because we need to integrate<br>> Sage Accounting APIs with our internal system.<br>> *Our Key Requirement:*<br>><br>> We have a *third-party system* used by our staff to request *Imprest /<br>> Expense approvals*, and we want this system to communicate directly with *Sage<br>> Kenya* (i.e., https://ke.accounting.sageone.co.za/) to post approved<br>> expenses.<br>> *Our Concerns:*<br>><br>>    1. *Too Many Links, No Clear Documentation:*<br>><br>><br>>    - We do not understand why we have multiple login URLs.<br>>       - Is https://ke.accounting.sageone.co.za/ specifically for Kenya?<br>>       - What is the difference between this and<br>>       https://accounting.sageone.co.za/?<br>>       - Which URL should we use for API integration?<br>><br>><br>>    2. *Lack of Country-Specific Documentation:*<br>><br>><br>>    - We need clear API documentation that applies to *Sage Kenya* and not<br>>       a generic guide meant for South Africa.<br>>       - Your API documentation should clearly define *what link to use<br>>       per country* and how to integrate with it.<br>>       - The response we received about the *Partner Entity Company Number*<br>>       was also unclear. Why not provide documentation for different regions<br>>       instead of using a South African format that does not apply to us?<br>><br>><br>>    3. *Frustrating and Unclear Process:*<br>><br>><br>>    - The multiple steps, different links, and unclear guidance make the<br>>       integration process unnecessarily complex.<br>>       - We have already submitted an API key request, but we are still<br>>       struggling with basic clarity on *which system instance we should<br>>       integrate with.*<br>><br>> *What We Need From You:*<br>><br>>    1. Confirm *which login URL* we should use for *API integration* in<br>>    Kenya.<br>>    2. Provide *country-specific documentation* (especially for Kenya) to<br>>    guide our integration.<br>>    3. Clarify the *Partner Entity Company Number format* applicable to<br>>    Kenya.<br>>    4. Explain why we were asked to create another account via a different<br>>    link.<br>>    5. Simplify the process—having multiple links is frustrating and a bad<br>>    user experience.<br>><br>> We appreciate your urgent feedback because this confusion is delaying our<br>> project. Kindly provide clear and precise responses so we can move forward<br>> without unnecessary back-and-forth emails.<br>><br>> Looking forward to your response.<br>><br>><br>><br>><br>><br>><br>><br>><br>><br>><br>><br>><br>><br>> On Fri, Feb 21, 2025 at 11:41 AM Kubushi, Joewie <<br>> JoewieHarvey.Kubushi@sage.com> wrote:<br>><br>> Hi David,<br>><br>><br>><br>> Kindly note that the Partner Entity Company Number is the number you<br>> received upon registering your business in your country.<br>><br>><br>><br>> Please note that the format previously provided is native to South Africa,<br>> meant to clarify what is required.<br>><br>><br>><br>> Please update the form with the registration number your company was<br>> issued with.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Friday, 21 February 2025 10:36<br>> *To:* Kubushi, Joewie <br>> *Cc:* ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za><br>> *Subject:* Re: Request for API Key<br>><br>><br>><br>> *EXTERNAL EMAIL*<br>><br>> Hi<br>><br>><br>><br>> I am  confused about where I am going to   find this information: *Partner<br>> Entity Company Number .* ?<br>><br>><br>><br>> On Fri, Feb 21, 2025 at 10:46 AM Kubushi, Joewie <<br>> JoewieHarvey.Kubushi@sage.com> wrote:<br>><br>> Hi David,<br>><br>><br>><br>> Kindly note that the Partner Entity Company Number refers to the company<br>> registration number in the format YYYY/NNNNNN/NN.<br>><br>><br>><br>> Please update your form accordingly.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>><br>><br>> *From:* Prof David Amukowa <br>> *Sent:* Wednesday, 19 February 2025 17:41<br>> *To:* Kubushi, Joewie <br>> *Cc:* ZA - SL - Pastel - MB - My Business - API <<br>> api@accounting.sageone.co.za><br>> *Subject:* Re: Request for API Key<br>><br>><br>><br>> *EXTERNAL EMAIL*<br>><br>> I have accepted the teams and Signed the Document<br>><br>><br>><br>><br>><br>><br>><br>> On Wed, Feb 19, 2025 at 1:42 PM Kubushi, Joewie <<br>> JoewieHarvey.Kubushi@sage.com> wrote:<br>><br>> Hi David,<br>><br>><br>><br>> Our API integration process begins with completing an enrolment form, in<br>> which you must agree to our Developer License Agreement. Please find<br>> attached the form for you to complete.<br>><br>> Once we receive your signed enrolment form, we will provide you with an<br>> API Key and URL for our Sandbox environment<br>> . Here,<br>> you can test your integration and notify us when your solution is ready for<br>> evaluation.<br>> We will investigate your Sandbox API Key logs to review the types of calls<br>> made during testing, which may lead to follow-up questions.<br>><br>> Please note that while we provide an API Key for you to code and test<br>> against in our Sandbox environment, we cannot guarantee that you will<br>> receive a Live API Key to use in our Production environment.<br>> During the evaluation process, a panel will assess your solution and<br>> determine whether it meets our criteria for use in the Production<br>> environment. Please be aware that there is no guarantee that a Live API Key<br>> will be issued.<br>><br>> The outcome of the evaluation will determine whether a Live API Key is<br>> issued or not.<br>><br>><br>><br>> Regards,<br>><br>> The Accounting API Team<br>><br>> [image: Sage]<br>><br>><br>><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>><br>> --<br>><br>><br>><br>><br>><br>> *David Amukowa *<br>><br>> *IT Consultant *<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>><br>><br>><br>><br>> --<br>><br>><br>><br>><br>><br>> *David Amukowa *<br>><br>> *IT Consultant *<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>><br>><br>><br>><br>> --<br>><br>><br>><br>><br>><br>> *David Amukowa *<br>><br>> *IT Consultant *<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>><br>-- <br>*David Amukowa *<br>*IT Consultant *