Webhook Response Issues

[Conor_McCormick]

So I've got a webhook set up that use the POST command to send lead records to a partner. The partner is receiving everything just fine, but when the make an update on their end to the record (about 10-20 minutes) after they receipt the information and send a response nothing happens - I see an API call was logged and they get a "200" return code, but the lead record on our end does not get updated at all.

Thoughts? I know I'm probably missing something basic about the functionality, but any insight would be appreciated.

[Kenny_Elkington]

Could you explain a little bit more about what's happening here?  You mention this:

>when the make an update on their end to the record (about 10-20 minutes

Are they trying to pass back changes 10-20 minutes later?  If so, how?  Webhook responses can only be mapped back to a lead record as part of the http response to the call being made, so if they've already responded, it wouldn't be possible to respond again without the webhook being called again.

[Conor_McCormick]

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 background or strong suit.

[Kenny_Elkington]

It's possible.  Have you asked your vendor if they're getting any errors, or seen any errors in your notifications?

[Conor_McCormick]

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 sorta good at something."

[SanfordWhiteman]

Need more info on an exact request and response payload.

Why does it take them 20m to generate a response?

[Conor_McCormick]

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 bit of experience working with posting info to Marketo, but did not have the proper command or filter to "updateLead" correctly, but we literally got everything corrected and squared away about 11 minutes ago. Things are humming along nicely now.

It's been quite the learning experience, and I truly appreciate the help and patience of the community.

[Anonymous]

Hi Conor - my first inclination is that there may be an issue with the association of the updates to the existing records. Can you verify whether or not a duplicate/new record was created by the API call?

[Conor_McCormick]

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?

[SanfordWhiteman]

This isn't a "webhook response" question really, if they're making a separate inbound call 20 minutes later. Webhook responses are the (synchronous) HTTP responses to webhook calls, not out-of-date traffic that might happen later. You should include an example of the exact payload they're sending.

Also, though this alone won't cause the problem, I hope their side is taking API limits into account. Generally speaking, webhooks are used instead of REST, not in addition.l

[Conor_McCormick]

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?