Can ChronoForms work like an API?

I would like to take advantage of the features offered by ChronoForms and use the component as a lead conduit moreso than a visible form. For example, I'd want to setup a form and then give my vendors the posting URL to my form so they can submit leads using the variables I created as if it were an API. (i.e. I'd give them http://www.mysite.com/index.php?option=com_chronocontact&task=send&chronoformname=test&firstname=xxxx&lastname=xxxx and they would post directly to this URL).

I understand there are security settings that will prevent this from working. Is there a workaround that will allow this to be done securely?

Thanks in advance for your help.

Hi dan76,

I'm not sure, you can certainly do this using a URL and get variables; you can do remote calls using AJAX. I don't see why it shouldn't be possible to do the calls using HTML Post too.

But it might require a hacked version of CF to bypass a security check. You can turn off the Joomla security token check; I don't remember if ChronoForms actually checks its own id or not (the code posted to a hidden field).

I think probably you could try it with a simple form and see if it works or not.

Bob

Thanks for your help. Unfortunately, I tried commenting out the token code and have checkToken turned off in the General section and it still doesn't work

I can get the form to submit without errors, so I'm going to have to double-check and find out why nothing saves to the table.

Hopefully I can get this working.

Hi dan76,

Does it save to the table if you submit it from within the site (rather than remotely)?

Bob

Hi dan76,

Does it save to the table if you submit it from within the site (rather than remotely)?

Bob

No, it doesn't. I'm going to try to work that issue out first. I found a good post in the forum where you offered advice on a similar issue. I've tried a lot of the recommendations there to no avail.

Hi dan76,

That makes sense ( I can't think of nay reason why it would save locally and note remotely).

Check for dashes in table, field and column names - they are the most common cause of failure to save.

Bob