Stupid Question - XML/API

[chileab]

I've read a lot about the auto-processing features in CommitCRM for XML emails. I'm familiar with XML, but I must be missing something, because I can't seem to find a DTD or schema for the XML document in the email anywhere. Am I missing something?

[Support Team]

Re: Stupid Question - XML/API

Hi chileab,

That's actually a great question :-)

The Email Connector's API by Email feature know how to receive XML-formatted emails and execute the transaction written in the XML email. This is actually considered part of our API, which includes a Programming API and the XML-formatted emails API (click here for more details regarding our API).

The API documentation includes the required XML format description and some samples. We usually provide the API documentation directly by request, to make sure anyone using the API understand the how to use it correctly. In case you wish to try it out, please contact us directly (at [ support @ ) and we will be happy to provide the relevant information.

Sherry

[chileab]

Re: Stupid Question - XML/API

Thank you, Sherry. I just sent an email to the address you gave. And if it is not in fact a stupid question, might I suggest adding it to your FAQ?

[Support Team]

Re: Stupid Question - XML/API

Yes, that makes sense - i guess people will be able to find it in this forum thread now :-)
I will also check whether we can add it in a more official place, thanks,

Sherry

[jtfinley]

Re: Stupid Question - XML/API

I have a guy who wrote a small WebApp that will be very usable for any mobile phone specifically the iPhone where you can select a customer, start/end time and quick charge detail and it will generate the XML email toCommitCRM. We're improving on this daily and is very promising...

[lpopejoy]

Re: Stupid Question - XML/API

Hey, that's a GREAT idea! Think it would work on the Blackberry?

How does it know what ticket to charge it for though? ...Or do you not use tickets?

[ajgyomber]

Re: Stupid Question - XML/API

This is really why CommitCRM need a SOAP XML API. It is so limited in its current form. It's only one way as you need ODBC to retrieve records out from the database. If I want to create a PHP page on my public web site to mobile-enable CommitCRM -- you can't to the best of my knowledge.

[Support Team]

Re: Stupid Question - XML/API

Hi ajgyomber,

Actually, in case you use the SQL Database for RangerMSP, we can provide you with direct PHP drivers which will allow you to pull information from the RangerMSP database via PHP code directly. Please contact us directly if you require this functionality.

Neta

[lpopejoy]

Re: Stupid Question - XML/API

Yes, but will you be able to read AND write with those PHP drivers?

--Luke

[Support Team]

Re: Stupid Question - XML/API

The PHP drivers can be used for read-only purposes.
In order to update information in the RangerMSP database you should use our edit/insert API. Usually when working via PHP, you would implement this by sending XML formatted emails from your PHP scripts, these XML transactions will then be processed by RangerMSP Email Connector and the database will be updated.

Neta

[ajgyomber]

Re: Stupid Question - XML/API

Do these PHP drivers need to be installed installed on the server? If so, I doubt that would be possible for many people that use shared hosting instead of a VPS or dedicated server.

[lpopejoy]

Re: Stupid Question - XML/API

AJ,

Probably be better off installing this stuff on your local network somewhere anyway so that PHP can access the DB locally instead of over a WAN. I don't like the idea of opening my CommitDB to WAN access - though I suppose you could limit that to a specific IP. At any rate, it would probably be a little slow - don't you think?

--Luke

[jtfinley]

Re: Stupid Question - XML/API

Neta,

We'd love to get the PHP Driver from you. Currently, the data is static for testing purposes and works great, but this driver would make it integrate very nicely. Our webapp now looks pretty good and is fast. We will integrate the login via SSL and COMMIT user DB if possible.