REST API: Error Code 1004 attributing lead to campaign by ID

[Anonymous]

We're currently receiving error code 1004 while attempting to attribute a lead to a campaign by lead ID. This behavior is unique to a specific client.

We deliver the lead data, the API returns a success response with an ID for that lead, we then use that ID to attribute the lead to a campaign, the API returns a failure: [{"code":"1004","message":"Lead [12345678] not found"}]}

Is there something the client could have done in their campaign setup to have caused this? I've tested on other accounts and campaign delivery is working fine.

Thanks

-Martin

[Kenny_Elkington]

Do you have an example request where you're receiving this?

[Anonymous]

Sure thing, see attached.

​Original file deleted.

[Kenny_Elkington]

Looking it over now, but you should probably delete that file and the associated custom service

[Kenny_Elkington]

I can't see anything wrong with the request itself.  If you try to get the lead by ID before or after trying to make the campaign request are you getting a response for that lead?

[Anonymous]

Yep, we're able to pull that lead from the customer's account using the ID manually.

Client is saying the lead does not show up in their lead database, although the API indicates otherwise? Is there something the client could be doing in their campaign to prevent leads from showing up for them?

[Kenny_Elkington · Accepted solution]

Unlikely, this probably needs to go to support.

[Anonymous]

Got it, thanks for your help Kenny.

[Anonymous]

Any luck with support?