Conor_McCormick

This is a good starting point for webhooks. If you are providing leads to the partner, you'd use a POST webhook to send info. For the partner to send information back to you, they'll need token access to the REST API.​ For technical info on updating the leads via the API calls see here.

They are calling out on leads we send them, then conducting a warm transfer if successful - as they make calls on them, they are sending status and activity updates, hence the turnaround time. Actually got everything squared away - my contact on their end had the right URL all along as he's had a bi...

They are getting the information perfectly, and when they post back to the api, they are getting a 200 return code, indicating success.Anyway, I feel pretty dumb about misunderstanding the webhook functionality, but like a great philosopher once said "Sucking at something is the first step to being ...

I think I didn't describe it correctly - they are passing back changes through the REST endpoint url. I think the problem may be that I only gave them the base of the URL and not the full xxxx/rest/v1/leads.json - would that be the issue?

I think I didn't describe it correctly - they are passing back changes through the REST endpoint url. I think the problem may be that I only gave them the base of the URL and not the full xxxx/rest/v1/leads.json - would that be the issue?As you might be able to tell, this is not exactly my backgr...

No duplicates in Marketo, and no records of merging. Is there anything specific I need to do to make sure it finds the right lead in the Marketo instance to update?

So got it mostly working, thanks for the assist. Turns out the partner actually didn't have it set up correctly on their end either, so even if I had it right, it would have rejected.

Oh crap. Stupid Stupid. I'll fix that.