This content has been marked as final. Show 3 replies
Would be better if you articulated your use-case. Marketo doesn't have any HTTP GET/POST endpoints that return meaningful data. We have one endpoint to which you can POST lead data, but to use a webhook, you'd have to have that info in the lead DB anyways.
I have two specific situations that I have:
I have two separate companies (think subsidiary) that have each their own MKTO. But since they are trying to be responsible from the parent company level re: data, we want to "alert" the other system if something changes (like an opt-out). Normally, I'd say middleware is the answer - but I'm trying to get away without it. 2nd scenario is I have partner companies that use MKTO themselves and would like to essentially "send" me a lead when they get it (or vice versa). Initially on that one I thought of using SOAP but it could cause issues because it would be a double-munchkin scenario.
All scenarios are more on the POST side of the house - but the first scenario would require MKTO to receive as well (not due to same webhook).
You could definitely POST to the other marketo instances using Webhooks. http://community.marketo.com/apex/MarketoDiscussionDetail?id=90650000000PYzlAAG describes all the params you'll need and you'll notice that the munchkin account Id is a mandatory one.
I'd also recommend that you go the API route for the first use-case where you have multiple subsidiaries, esp if you don't want to deal with a lot of troubleshooting to ensure that the data is in sync across multiple instances. The Webhook POST seems like a viable candidate for the partner use case.