How to find 1018 REST API error origin? | Community
Skip to main content
Will_Craig
Will_Craig
Level 2
January 2, 2020
Question

How to find 1018 REST API error origin?

  • January 2, 2020
  • 1 reply
  • 2398 views

We're receiving notifications for this 1018 REST API error - but I don't see a way of finding where the request is coming from - is there any way to look at the origin of these errors?

https://nation.marketo.com/docs/DOC-4594-rest-api-error-1018-crm-enabled-the-action-could-not-be-carried-out-because-the-instance-has-a-native-crm-integration-enabled 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
January 3, 2020

This is reason #1 that passing all Marketo API calls via an API gateway is advisable. You just don't have that visibility.

Without the gateway, you have to start switching off integration users until the errors stop -- you'll be disabling production connections as well, and the integration that's triggering this error may be doing other things right.

Will_Craig
Will_CraigAuthor
Level 2
January 3, 2020

Do you have an implementation guide for that?

SanfordWhiteman
SanfordWhiteman
Level 10
January 3, 2020

Depends on the platform. With AWS API Gateway it's pretty much a standard Proxy config. That's AWS's catchall config, for all API methods exposed by a certain host, like {Munchkin ID}.mktorest.com.

Not to say it's easy to get up to speed, but the individual config for Marketo (once you have the grounding) only takes a couple of hours to test and deploy. Again I don't want to portray this as easy, just necessary.

Terms & ConditionsAccessibility statement

Loading footer...