Show which LaunchPoint (web API) service is responsible for specific change or lead create

[Anonymous]

Implement a way for the customer to find out which LaunchPoint service is responsible for a specific change through API. An example would be a data value change on a person record that was done via API but we have no way to know which LaunchPoint service was the source of the web API call.

[SanfordWhiteman]

I agree that this would be useful, but an easier workaround is to use the Push Lead endpoint, which specifically contains a Reason field as part of the call. I use this to contain the service parameters.

[Grégoire_Miche2]

Quick question, what are the DVC reasons and source containing when the value change is triggered by an API call?

Greg

[Amy_Goldfine]

Interesting, Sanford can you explain more of how that works?

[SanfordWhiteman]

The Push endpoint accepts two optional freeform string values, source and reason, which supplement the Program membership that's required as part of the call.

So you can (almost always) use one of those fields to denote deeper information of the API caller.

Of course it's to some degree on an honor system, because the fields are freeform. That is, the remote client must deliberately follow your procedure because the fields are optional. But you can send an alert on updates that do not include one of your allowed values.