SOLVED

Filtering Bulk Activity Extract API by List ID

Go to solution
Highlighted
Level 1

Filtering Bulk Activity Extract API by List ID

Hi -- I have a question about the Bulk Activity Extract API. Is there a way to filter it by the list id? I tried the following codes, but it didn't work:

{
"format": "CSV",
"filter": {
"staticListId": 12345,
"createdAt": {
"startAt": "2019-08-01T00:00:00-00:00",
"endAt": "2019-08-31T23:59:59-00:00"
},
"activityTypeIds": [
1
]
}
}

{ 
"format": "CSV",
"filter": { 
"listId": 12345,
"createdAt": { 
"startAt": "2019-08-01T00:00:00-00:00",
"endAt": "2019-08-31T23:59:59-00:00"
},
"activityTypeIds": [ 
1
]
}
}

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 5

Re: Filtering Bulk Activity Extract API by List ID

Pretty sure that filter is only for the Lead Extract:

https://developers.marketo.com/rest-api/bulk-extract/bulk-lead-extract/#filters 

Bulk Activity will let you filter by activityId but that will give you all 'Added to List' activities. You could filter this further in your code but seems like this strategy would extract more data than what's needed. 

View solution in original post

3 REPLIES 3
Highlighted
Level 5

Re: Filtering Bulk Activity Extract API by List ID

Pretty sure that filter is only for the Lead Extract:

https://developers.marketo.com/rest-api/bulk-extract/bulk-lead-extract/#filters 

Bulk Activity will let you filter by activityId but that will give you all 'Added to List' activities. You could filter this further in your code but seems like this strategy would extract more data than what's needed. 

View solution in original post

Highlighted
Level 1

Re: Filtering Bulk Activity Extract API by List ID

Got it. Thanks, Mark!

I also tried exporting activities calling this endpoint (https://developers.marketo.com/rest-api/lead-database/activities/) but it became so time-consuming as I couldn't find a way to automate the process. 

Highlighted
Level 10 - Community Moderator

Re: Filtering Bulk Activity Extract API by List ID

Weird that you'd say that IMO, because using the paginated Activities endpoint is easier to automate than the Bulk Extract, since it doesn't require any polling or job coordination.  You just charge straight through, following each new page (and of course being ready to refresh the token as necessary).