Distinguishing between API web services in Activity log | Community
Skip to main content
A
Anonymous
October 2, 2018
Question

Distinguishing between API web services in Activity log

  • October 2, 2018
  • 1 reply
  • 2069 views

We have marketo syncing with a FileMaker database through a lot of custom scripting.

Part of the custom scripting is getting lead data changes through the activities API and updating our database accordingly. 

One problem I've run into is that we don't want to have changes that were pushed up from the FileMaker database to Marketo to then be written back down to the FileMaker database again when we are going through the lead activity.

The FileMaker database is not the only thing connecting and making changes through the Web API.  However, both the "Reason" and "Source" attributes for the activity simply say "Web Service API".  This isn't enough information to filter our the changes from FileMaker.

Is there any way to set up a system to be able to tell where the Web Service API changes are coming from?  A setting, custom activity, or whatever?

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
October 2, 2018

Which REST API endpoint are you using to write data?

A
Anonymous
October 2, 2018

leads.json through the REST api.

SanfordWhiteman
SanfordWhiteman
Level 10
October 2, 2018

You should switch to the Push Lead (/push.json) endpoint, which lets you include a call-specific source and reason with the payload.

Terms & ConditionsAccessibility statement

Loading footer...