Marketo - How to use the generic blocks

[Ionut_Dumitrascu]

This article gives an overview of the available generic blocks in the Marketo connector in Qlik Application Automation. It will also go over a basic example of using these blocks.

The generic blocks are meant to be used in case you need to use an endpoint that it's not natively configured.

The following generic blocks are available:

• API List Request
• API Get Request
• API Create Or Update Request
• API Delete Request

All these blocks have an input called 'Endpoint Url' which needs to be filled in accordingly based on what API is used, and on what object you need to work with.

Because Marketo is using different kinds of solutions for the same use-case (example: for paging, both cursor and offset based paging are used), some blocks are limited to one use-case: the 'API List Request' block is limited to use cursor paging and the 'API Delete Request' block is only available for the Marketo 'Leads' API.

Now let's go over a few examples of using the 'API List Request' for both the 'Leads' and also the 'Assets' API from Marketo.

1. Leads API: for this API, the basic endpoint URL has the following format: v1/{object}.json, where '{object}' needs to be replaced with an actual object from Marketo, for example, 'leads'. This particular example also requires a few query parameters to be filled in. For this, use the input for the 'Query parameters' and provide the required parameters to be able to query for leads.

2. Assets API: for this API, the basic endpoint URL has the following format: asset/v1/{object}.json, where '{object}' needs to be replaced with an actual object from Marketo, for example 'programs'.

For additional info on how other requests need to be configured, please check out Marketo's API documentation.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.