Hi Raj-
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).
thanks,
Brigid