Kenny_Elkington

That's your issue. Admin is not an API role. You need to add a role that specifically has those API permissions to the user for it to access data in that workspace. This should give you the info you need: Custom Service » Marketo Developers ​

In the Admin > Users & Roles menu, when you look at this user does it have a role with the Read-Only/Read-Write Lead permission in both workspaces?

Do you have workspaces and partitions in the target instance? If your user doesn't have access to the workspace where one of the lists is then nothing would be returned in that case. Providing the info that Grant suggested would also be helpful.

Generally using the data of the most recently retrieved activity as a high watermark is the best way. You can use this to retrieve a new token for subsequent retrievals.

Forms are rendered from Javascript, and don't have a static HTML representation. What are you trying to accomplish?

Marketo Webhooks can't be called synchronously with page views, so I would say that this is the wrong approach. I would look into doing this via AJAX in the browser, or proxied through your own server.

Marketo is agnostic to file types(unless you have file type filtering enabled). Regarding content-type, you should use a method which derives content-type by the file extension. These are available in practically every language used commonly for web development and are far more reliable than doing...

Well this isn't completely true. My tokens are perfectly valid for use in interesting moments, but they will only populate correctly when the smart campaign which is creating them is a child of the program. The flow step inherits context for my tokens from the campaign, not from the triggering ass...

Are you going to be using a middleware provider for the integration? I don't think any of our partners' existing integrations support that flow out of the box. If you're rolling your own, it would be possible but definitely not easy in any sense.

Steps with the same value can be moved to and from freely, without the same restriction as the normal only-move-forward pattern that program statuses have. It's very typical to have RSVP and Declined on the same value so that they can be freely altered if an invitees plans change.