How do I identify and locate the Ecommerce fields in Infusionsoft’s backend to send data from Infusionsoft to another application? I’m using an Infusionsoft landing page and Ecommerce order form to collect payment from an Infusionsoft landing page for a monthly subscription to a service built on a Laravel platform. I need to also identify a list of details to collect at the time of the transaction.
You can try looking at these endpoints:
Hopefully, they can help you with that.
Hi Vasanth, as I understand this documentation is helpful for retrieving data into Infusionsoft. I’m using Infusionsoft/Max Classic Ecommerce and need to determine how to “push” subscription and transaction data to my outside application portal. Your thoughts?
Probably these endpoints can be helpful in getting subscription and transaction data from your Infusionsoft/Max Classic Ecommerce.
GET subscription data
GET all transaction data
GET a specific transaction
Hope this helps.
Hi Vasanth, thanks again! I provided the above info to my developer but he says we need Infusionsoft to “push” the subscription details to my application when a person completes a transaction.
Hi Vasanth, thanks again! The objective is to use Infusionsoft as the “source” for the API to push data i.e. subscription, transaction, etc details to my applciation as the “endpoint” for mySQL. How can this be done using Infusionsoft API?
You have to create a middleware code set. So you make your own endpoints with PHP/Python that receives information and then uses that data in connection with a database (mySQL) connection. It’s a bit involved if you’re not familiar with it so it’s not something you’re going to just quickly work out on your own all that quickly…not saying you can’t work it out but you’ll need to know PHP/Python, SQL, web tech action protocols like http/https and/or curl etc. It’s a lot to learn if you’ve never done it before. So depending on how much time you have on your hands and how much prior programming experience you have, you may need to consider hiring a developer that specializes in this.
Rest Hooks are a great way to programmatically alert another system of things happening within your Keap App. I would recommend leveraging these along with your subscription triggers to automate management of active/inactive subscribers and billing within Keap.
Here are the current list of event_keys available for Rest Hooks:
[ "appointment.add", "appointment.delete", "appointment.edit", "company.add", "company.delete", "company.edit", "contact.add", "contact.delete", "contact.edit", "contact.redact", "contactGroup.add", "contactGroup.applied", "contactGroup.delete", "contactGroup.edit", "contactGroup.removed", "invoice.add", "invoice.delete", "invoice.edit", "invoice.payment.add", "invoice.payment.delete", "invoice.payment.edit", "leadsource.add", "leadsource.delete", "leadsource.edit", "note.add", "note.delete", "note.edit", "opportunity.add", "opportunity.delete", "opportunity.edit", "opportunity.stage_move", "order.add", "order.delete", "order.edit", "product.add", "product.delete", "product.edit", "subscription.add", "subscription.delete", "subscription.edit", "task.add", "task.delete", "task.edit", "user.activate", "user.add", "user.edit" ]