API Manual/Implementations

First off, is their a user guide to Commit's API? I looked all over, but didn't see anything... What am I missing?

Second, I would be interested to hear how people have deployed the API - some scenarios, etc...

Thanks,

Luke

Luke,

Open up a support ticket and they will get the API document to you. Last I knew it was still in beta so it was not posted publicly, but it has been working well for us. To read data they provide an ODBC interface to the database. To write records to the database you can either interface directly via program code and the API, or you can submit XML formatted emails to the email connector. The latter is what we have been using.

If you have this in hand the stuff I have been talking about adding ourselves will become much more clear. If it has to do with adding tickets, charges, contracts or contacts to the database we can do that.

Vernon Southmayd
http://commitusers.uservoice.com

I just wish N-Able would allow me to create XML email templates...

I am assuming N-Able does not let you change the format of their Email alerts. I do not have Kaseya inject XML alert emails into CommitCRM directly. I am using the CommitCRM Email Connector to add tickets inCommitCRM.

Again assuming, but my guess is that the things you want to move from N-Able to CommitCRM are tickets and assets. You will need something that acts as middleware between the two packages translating API fields between the packages. This is how Autotask and Connectwise make their integrations. My goal in the poll is to identify what people are looking to convert into CommitCRM and to go after building that MSP connector using the different vendors APIs.

Can you point me at or get us a copy of the N-Able API?

Vernon Southmayd
Creative Computing, Inc.
http://commitusers.uservoice.com

I just found several pages on how to integrate CommitCRM with N-able (I haven't tried it though).

Here's the link

I was told by N-Able that CommitCRM asked for their API documentation. I'm hoping we'll see something in the next release but who knows.

So it sounds like there is no publicly available API from N-able?

Vernon

I'm not sure. I'll have to ask the product specialist I am dealing with.