Skip to main content
Dan_Stevens_
Level 10
Mar 4, 2017 8:02 PM UTC
Solved

Anyone experiencing issues with calling a local webhook?

We have a webhook setup to create leads using our local endpoint URL (localhost/index.php/leadCapture/save).  This has been working fine for years.  Detail when calling the webhook looks like this:

Now, nothing happens.  And the detail looks vastly different:

Anyone here experiencing similar issues?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Dan_Stevens_
Dan_Stevens_Accepted solution
Level 10
Mar 4, 2017 8:53 PM UTC

False alarm.  As this was all part of some testing we're doing (using batch campaigns), the "1000" error code resulted:

Which is actually odd since we use batch campaigns for other calls to webhooks - e.g., Informatica email validation - which work perfectly fine.

3 replies

SanfordWhiteman
User Group Leader
User Group Leader
Mar 4, 2017 8:26 PM UTC

There's been a recent change with the /save endpoint that I've noticed with an older forms integration. Give me a zap via email and we can talk about it.

Translate
Dan_Stevens_
Dan_Stevens_AuthorAccepted solution
Level 10
Mar 4, 2017 8:53 PM UTC

False alarm.  As this was all part of some testing we're doing (using batch campaigns), the "1000" error code resulted:

Which is actually odd since we use batch campaigns for other calls to webhooks - e.g., Informatica email validation - which work perfectly fine.

Translate
SanfordWhiteman
User Group Leader
User Group Leader
Mar 4, 2017 9:20 PM UTC

I'm sure if you look at the other campaigns, they're actually batch-to-trigger, not batch alone (i.e. they call ​Request Campaign or update a data value).

The change to the /save endpoint is w/external connections, I guess it's not affecting loopback conns given your update.

Translate