Mykhailo_Starod

Thanks.  "Latest Lead Source" field value is defined at the upstream system. Did I understand you correctly? ... View more

Thank you for your answer. The REST API endpoints aren't webhooks. That's the reverse direction. I mean our downstream system handles lead creation webhook from Merketo. But the main problem is the identification of API user who creates leads. We take it further and have every API connection come in via an API   gateway.  That gateway always tags the inbound call with the identity of the requester, so they don't have to remember to include it. Did you create a reverse proxy over Marketo? Does this proxy have its own authentification to identify users? Is it possible to build this solution under Marketo infrastructure? ... View more

No, unless you manually pass it as a field. Duplicate system time zone in the webhook template is not a good solution. Does it possible to request a new system token: {{system.timezone}}? An alternative solution is to provide a possibility to set date format in the token: {{createdAt:format=yyyy-MM-dd'T'hh:mm:ssZ}} It's valid ISO 8601 local. I don't know what you mean by "best practice" unless you're referring to the absence of an explicit timezone for transport outside the system. Yes. L ocal date is fine for user interface but not for the system to system communication .  ... View more