API Troubleshooting | Community
Skip to main content
Nina_Gonzalez1
Level 3
March 22, 2018
Question

API Troubleshooting

  • March 22, 2018
  • 2 replies
  • 4459 views

I'm working with a marketing partner on a REST API. It was working for two forms and now only working for one form. So most of what they are doing is working. Based on usage report I can see that there are API hits for both forms. But no leads from one form and no error messages. I'm told Marketo does not give access to API logs, so trying to determine how to troubleshoot. Any ideas? Is there a developers forum?

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

2 replies

Stephen_Baker2
Level 2
March 22, 2018

Do you have more details on what determines the requests being successful even though it appears to not work? Are you observing 200 statuses AND responses with a body that contains a success status?

Nina_Gonzalez1
Level 3
March 22, 2018

I can see that the number of API calls is too high for testing against just one form, so I am assuming that both forms are hitting the API. But that is not definitive proof that the requests are being successful.

SanfordWhiteman
Level 10
March 22, 2018

I can see that the number of API calls is too high for testing against just one form, so I am assuming that both forms are hitting the API. But that is not definitive proof that the requests are being successful.

Definitely not, since you're not seeing the error messages in the response.

On the usage note, did these people build in a rate limit and daily max?  Because otherwise they're creating a DoS vulnerability against your instance. Any outside service should enforce an internal cap and rate limit.

SanfordWhiteman
Level 10
March 22, 2018

You need to supply far more info.

The outside partner should have complete HTTP request/response logs of what they're sending. You can post the JSON payloads here (please use the syntax highlighter in Advanced Editor).

Nina_Gonzalez1
Level 3
March 23, 2018

This is not solved yet, but thanks to your help we are making progress. Thank you. When looking at the HTTP request/response, there was an error because the date format was not correct.