>Will there be any time before the switch-over that the API returns both the new “marketoGUID” string field and the existing ActivityId? We may be adding this in our Minor release next month. I'll share this when I'm certain. >Is there a way to switch an instance over to this prior to the Spring 2017 release? This this change is coming as part of an infrastructure rollout, so coordinating cutover would be difficult at best. > If the MarketoGUID is not available when the current ActivityID becomes unreliable, how should we uniquely identify an Activity record? You shouldn't have to face this scenario >When can we expect the API documentation to be updated to include the new “marketoGUID” field? We'll try to get this all updated for the "how-to" docs over the next few days to a week. The endpoint reference will need to wait since it's generated from code > Will old activities be back-filled with the “marketoGUID” field? Yes. > Does Marketo plan to use versioning in their REST APIs going forward? Yes. Versioning would not help in this case however, since our infrastructure will no longer provide the means to generate a unique integer ID in the same way. >Should we expect other breaking changes with short time-frames like this in the Marketo API going forward? This situation is somewhat unique because our infrastructure is pushing this change onto our public interface. Whenever possible, we'll give as much advance warning as we possibly can.
... View more
.png?67D10DF4A500B5C9CAD6D9D40B974747)