Get rmm agent installer link through api?

I have made it so a a customer fills out a fourm on my website it then creates a customer in sycnro and emails them the portal invitation, the next step i need is to also email them the rmm installer,
i had a look at the api and cant find anything and cant find anything on the customer page that indicates how the link is generated, is there a way to do this?

i know i can use a default customer to have a constant link but i am doing this so its all automated and need it linked to that customer

1 Like

a bit of fiddling around but the id in the command line one does not match the customer id so its impossible to use, a bit more digging i found its getting all the installers from either or and its generating a token but the token is being generated from a kabuto customer id and not the syncro customer ID, seems a bit of a mess really i thought i had moved off of kabuto but i guess you guys kepts the old system going, so i need to know how to get this kabuto ID with your syncro api.

1 Like

Hi @forfar, can you submit a ticket and I’ll have support look into this.

I’ll be 100% interested in these results if you don’t mind sharing them afterward! Looking to get this setup for myself too.

not heard back from syncro yet but in playing around with it i have found you can get the kabuto customer ID through zapier, going to see if i can get it through my own api calls now

ok i swear this was not there before, but in retreive customer by ID you can get kabuto customer ID. i think they may have added it?

1 Like

hmm does not work on new customers as it returns null , then also need to figure the folder id out

need to figure out a way to run this link when a customer is created .

1 Like

I had a look at this.
get /customers does not show the kabuto_customer_id
Even when putting a customer name in to query, the kabuto_customer_id does not appear.
get /customers/{id} does show the kabuto_customer_id
Even for the same customer name that I previously put into the query field when using /customers without an id.

Of course, nothing is mentioned in the API documentation.
I’ll log a support ticket for this.

If they have modified the API, without updating the API documentation that would be bad.

I have not looked at this for a few months but we were looking at how we could get the agent installed from API calls also.

We found that Syncro does not have the kabuto id you need for the RMM until you get the Syncro (web pages) to generate a link. So for any customers that have not yet had an agent installed you have to use other methods.

We had tried to maintain a dummy customer, where you know the link. Then you can use the API to move that asset to the correct customer and policy. This can be tricky as you are at the mercy of the speed of the machine and the Syncro agent to get you to the point where you can get the kabuto id off the asset (it’s stored in the registry).

The other problem of trying to generate your own links is that the policy id’s are not accessible from the API so you have to maintain a separate table. If you have customers that need different policies than the root level you will need to have that someplace you can reference.

Our current method we manually add a link to the ticket(s) in the ticket comments when first creating the tickets and via API we can scrape the link out of there.

1st, create a customer called TestBusiness. Do nothing else in the WebUI for the customer.
2nd, Then following the process below use the documentation page for the API to retrieve the customer record for TestBusiness

  1. Unfortunately kabuto_customer_id is not in the documented example value for the get /customer API
  2. Search for a customer called TestBusiness using the get /customer API
  3. You will see that kabuto_customer_id does not appear in the API response of get /customer
  4. Notice also that kabuto_customer_id is not in the documented example value for the get /customer/{id} API either
  5. Copy the id value from the data returned for TestBusiness from the get /customer API
  6. Use the id value in 5, to execute the get /customer/{id} API
  7. Now you will see that kabuto_customer_id is in the response from the get /customer/{id} API, even though it is not listed in the documentation example value for the get /customer/{id} API

I’ve already logged a support ticket to get the documentation fixed.
Strangely enough, I had a email from the RepairShoppr support team seeking further information. I sent them the above process complete with a video. The above process is reworded a little to suit posting here.

Just guessing here and not tested.

Previously kabuto id’s where not an immediate thing, it used to be that creating an RMM link took 10 seconds on average the first time it was used, after that it was instant to get a link. The kabuto id would then show in the API also at that point.

More recently the links are all pretty much immediate. It could be that Syncro are allocating the kabuto id’s soon after a new customer is created and you don’t need to force allocation, just need to wait a while.

The documentation examples do miss quite a lot of extra fields you can have access to and are really only a starting point, especially try if you are trying to write to the ticket/customer etc.

The Syncro/RepairShopr guys are good at helping out where they can.

i wonder if we should create a thread where everyone working with the api shares all its nuances and hidden features? or ways we have worked with it the more visible the more development we may get on it

1 Like

check out
Latest Scripting & APIs topics - Syncro Support Community (

yeah after a bit of testing I couldn’t force it to do it(tried updating customer by id) but yeah wait about 10 mins and it appears, will probably create my own installer program so once the customer registers pays then downloads it should have hopefully been generated, pass in customer id to my installer so when it does generate kabuto id I can move the customer to the correct account automatically. now need to find a way for the customer to add a payment method so i can create recurring invoices.

Can’t the customer add a payment method from the user portal?

they can but my thinking is if there is too many steps, ie, signup on website go to emails downlaod tool, wait 10 mins for recurring invoice to be made then login/signup to portal account read external intructions on how to add a payment method the customer will just get lost and give up, i have however starting to create an ElectronJS app that will hopefully contain all of these steps in one platform so that may make the current method a bit more user friendly, will share it when im done.

I have managed to create a universal installer that you can give the customers, they input there email and it downloads and installs to the correct syncro account,
I made this is electronJS so i can share this on gitbhub if anyone would just have to input your own details which can be found in apps /agnent installer in syncro. if people want this i will package it up and take my details out. I found syncros own powershell scripts for when you are onboarding customers from another rmm and translated this to javascript

1 Like