Named Account Lists

Named Account Lists in Marketo represent collections of named accounts. They can be used for a wide variety of cases, including categorization, data enrichment, and smart campaign filtering. The Named Account List APIs allow for remote management of these list assets and their membership.

Permissions

To query Named Account Lists, the Read-Only Named Account List or the Read-Write Named Account List permission is required. To Create, Update, or Delete Lists, the Read-Write Named Account List permission is required. Querying list membership requires the Read-Only Named Account or Read-Write Named Account permissions, while managing membership requires the Read-Write Named Account Permissions.

Model

Named Account Lists have a very limited number of standard fields, and are not extensible with custom fields.

Named Account List Fields

Name

Data Type

Updateable

Notes

marketoGUID

String

False

Unique string identifier of the named account list. This field is system managed, and is not permitted as a field when creating a new record. Field used by “dedupeBy”:”idField” when performing a create or update.

name

String

True

Name of the list. Field used by “dedupeBy”:”dedupeFields” when performing a create or update.

createdAt

Datetime

False

Datetime of the creation of the list. This field is system managed, and is not permitted as a field when creating or updating a record.

updatedAt

Datetime

False

Datetime of the most recent update to the list. This field is system managed, and is not permitted as a field when creating or updating a record.

type

String

False

Type of the list. May have a value of either “default” or “external”. External lists are those created by CRM Account View.

Query

Querying account lists is simple and easy. Currently, there are only two valid filterTypes for querying named account lists: “marketoGUID” and “name”. The field to filter on is set in the “filterType” parameter of the query, and the values are set in “filterValues” as a comma-separated list. The nextPageToken and batchSize filters are also optional parameters.

Create and Update

Creating and updating named account list records follows the established patterns for other Lead Database create and update operations. Keep in mind that named account lists only have one updateable field, “name.” The endpoint permits the three standard action types, “createOrUpdate,” “createOnly,” and “updateOnly.” The “action” defaults to “createOrUpdate.” The optional “dedupeBy” parameter permits the values “dedupeFields,” corresponding to “name,” or “idField,” corresponding to “marketoGUID.” In createOrUpdate and createOnly modes, only “name” is permitted as the dedupeBy field. You can submit up to 300 records at a time.

Request

1

POST/rest/v1/namedAccountLists.json

Body

1

2

3

4

5

6

7

8

9

10

11

12

{

"action":"createOrUpdate",

"dedupeBy":"dedupeFields",

"input":[

{

"name":"SAAS List"

},

{

"name":"Manufacturing (Domestic)"

}

]

}

Response

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

{

"requestId":"e42b#14272d07d78",

"success":true,

"result":[

{

"seq":0,

"status":"updated",

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb"

},

{

"seq":1,

"status":"created",

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fc"

}

]

}

Delete

Deletion of Named Account Lists is simple, and can be done based on either the name, or the marketoGUID of the list. To select the key you wish to use, pass either “dedupeFields” for name, or “idField” for marketoGUID in the deleteBy member of your request. If unset, this will default to dedupeFields. You can delete up to 300 records at a time.

Request

1

POST/rest/v1/namedAccountLists/delete.json

Body

1

2

3

4

5

6

7

8

9

10

11

12

13

14

{

"deleteBy":"dedupeFields",

"input":[

{

"name":"Saas List"

},

{

"name":"B2C List"

},

{

"name":"Launchpoint Partner List"

}

]

}

Response

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

{

"requestId":"e42b#14272d07d78",

"success":true,

"result":[

{

"seq":0,

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb",

"status":"deleted"

},

{

"seq":1,

"id":"dff23271-f996-47d7-984f-f2676861b5fc",

"status":"deleted"

},

{

"seq":2,

"status":"skipped",

"reasons":[

{

"code":"1013",

"message":"Record not found"

}

]

}

]

}

In the case that a record cannot be found for a given key, the corresponding result item will have a status of “skipped” and a reason with a code and message describing the failure, as shown in the above example.

Managing Membership

Query Membership

Querying the membership of a named account list is simple, requiring only the id of the account list. Optional parameters are:

“fields” a comma-separated list of fields to include in the response records

“nextPageToken” for paging through the result set

“batchSize” for specifying the number of records to return

If “fields” is unset, then “marketoGUID,” “name,” “createdAt”, and “updatedAt” will be returned. “batchSize” has a maximum and default value of 300.

Request

1

GET/rest/v1/namedAccountList/{id}/namedAccounts.json

Response

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

{

"requestId":"e42b#14272d07d78",

"success":true,

"result":[

{

"seq":0,

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb",

"name":"Saas List",

"createdAt":"2017-02-01T00:00:00Z",

"updatedAt":"2017-03-05T17:21:15Z"

},

{

"seq":1,

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fc",

"name":"My Account List",

"createdAt":"2017-02-01T00:00:00Z",

"updatedAt":"2017-03-05T17:21:15Z"

}

]

}

Add Members

Named accounts can easily be added to a Named Account List. Accounts may only be added using their marketoGUID. You can add up to 300 records at a time.

Request

1

POST/rest/v1/namedAccountList/{id}/namedAccounts.json

Body

1

2

3

4

5

6

7

8

9

10

{

"input":[

{

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb"

},

{

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb"

}

]

}

Response

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

{

"requestId":"string",

"result":[

{

"seq":0,

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb",

"status":"added"

},

{

"seq":1,

"marketoGUID":"dff23271-f996-47d7-984f-f2676861b5fb",

"status":"added"

}

],

"success":true,

}

Remove Members

Removing records from an account list has a different path, but the same interface, requiring a marketoGUID for each record that you want to delete. You can remove up to 300 records at a time.

Latest Blog Posts

Keep up with what's new in the developer world

Important Change to Activity Records in Marketo APIs March 1, 2017 Note: This post will be updated to reflect changes made to activity records returned by the API due to migration to new infrastructure.
With the rollout of Marketo’s next-generation Activity Service beginning in Septmeber, we will be unable to enforce the uniqueness or presence of the integer “id” field in activities, data value changes, or lead deletion ... Read More >

Internet of Things for Marketers with IFTTT and Zapier June 20, 2017 The Internet of Things (IoT) is the inter-networking of connected devices, appliances, wearables, vehicles, etc. with embedded electronics, software, sensors, and network connectivity that enable these objects to collect and exchange data with cloud information systems. These technologies are growing and trending so fast that they will impact how we live, how we work and ... Read More >

Spring 2017 Updates June 16, 2017 In the Spring 2017 release, we are adding the ability to bulk extract lead and activity object data asynchronously, and to manipulate named account lists. See the full list of updates below.
Lead Database APIs
Bulk Extract of Leads
New endpoints to support extraction of leads in bulk. Specify record selection criteria using a variety of options. Details can ... Read More >