Web services error codes

[Ken_Soldink]

We consistently get error codes 1003 and 1006 and I cannot find these definitions in documentation anywhere..

Anyone have any experience or idea what these codes means?

Thanks,

_Ken

[Anonymous]

I wish Marketo would list the API user that triggered the error, include the definition beside the error code, and include the other details that are captured in their log. That'd make troubleshooting a little easier.

[Kenny_Elkington]

This is a good idea.  I'll see what we can do.

[Luke_Wotton]

Has anything happened on this? The only option is to query support on it every time.

[markfarnell]

this happened to me today - looks like we still have to raise a ticket with support! 

[Brett_Carpenter]

Has there been any progress on this Kenny Elkington?

[Dan_Stevens_]

We just ran into this today with a 604 error.  I needed to create a Support ticket for them to provide me with the additional information so that I could alert the team/app that caused this.  Having this insight within the UI/alerts is sorely needed - especially given how popular the API is.

[Luke_Wotton]

I was just thinking the same thing.

[Anonymous]

Awesome! Thanks, Kenny!

[Kenny_Elkington]

You can find a full list of codes here: Error Codes » Marketo Developers

1003 means that a business rule was violated by the data submitted in the call.  The specifics will be variable according to the type of call and the request made.  If you have an example request we could let you know why you might be getting it.

1006 means that a field was submitted for a Lead, Company, Opp...etc. which does not exist in the target instance.  If you catch and log the response, it should provide the name of the invalid response.

[Leanne_Persang]

Hi all,

I received multiple 609 codes over the weekend:

Looking at the list of developer codes, this means:

Knowing that, any idea what action I need to do in order to fix the error?

Thanks for your help!

[SanfordWhiteman]

You have to find the client app that caused the error.

Then make sure the JSON stringifier and related request logic always passes valid JSON.

It's impossible to say more without a look at an offending payload. JSON syntax is extremely well-known, so if you're using a standard JSON encoder (i.e. not building your own JSON string) I expect the problem is more like an undefined/empty var, etc.

[Leanne_Persang]

Thanks for your response, Jason. Unfortunately, I am not a developer - where do I look for an undefined/empty var, etc.?

[SanfordWhiteman]

What are the apps that consume your REST services? That's where the error is occurring.

[Anonymous]

1003 is usually an authentication error, 1006 is service could not be contacted

Both of these are based on my experience, may not be precisely correct in this case

[Ken_Soldink]

Thanks Jamie. Do you know where I can dive into the actual error message attached to the codes? Like what lead or smart campaign or service triggered the authentication error, or timeout? There's no actual information I can review to determine what's causing the errors, and how to fix them.