Kenny_Elkington

Yes, by updating content sections: http://developers.marketo.com/documentation/asset-api/update-email-content-in-editable-section/

Sorry, that's my mistake, I was confusing it with REST, there are no list or describe operations for custom objects in our SOAP API. You'll need to use the REST operations to get that data.

You have the $ and { swapped in your image. Flip their positions and it should work.

You can use the process you described, list for available objects, and describe for fields, but REST will be faster and more robust. We don't recommend doing any new development in SOAP.

I know it will under certain circumstances where the path is broken or incomplete and a 403 is returned, but it doesn't seem like you're getting that here. It would be hard to say unless you can get the raw response from your client

You'd normally get a 414 if the request URI were too large (over 8k), so if you're getting a 200 and then the bad line, then it would not be that specifically.

This is probably something you should work with Support on. I haven't dealt with these sorts of access issues directly in quite some time.

I don't have access to them, but I would guess that the template is something like this:'Changed %s1 from "%s2" to "%s3"'The real template will depend on the language you're using though.s1 is the name property from Describe Lead for the field, with the field being mapped from the id in the change t...

I see now. This is actually a virtual field which is templated when viewing an activity log/campaign results, not a database field, so we would not return it via the API. You could create display templates to mimic this in your external system, though.

Do you have an example of what you're looking for here?