API, same request for activities endpoint having 2 different responses (for old data)

Anonymous
Not applicable

API, same request for activities endpoint having 2 different responses (for old data)

Hi all, a Tableau wdc user using Marketo's connector reported a difference between 2 identical requests done in about 34minutes difference, the paging token correspond to data stored on May 2016 so we assume it's not related to new data being stored. ( the number of records and the newxPagingToken are different ).

Is there a process triggered by the request on Marketo's side that affects the result?

Thanks

Here the request/response info ( sensible data replaced with ***** )

REQUEST A

GET https://****mktorest.com/rest/v1/activities.json?nextPageToken=MHFDCYN5AZMK5QHZ5P7FM4SNFH6AI2UQM6LEY... HTTP/1.1

Accept: application/json, text/javascript, */*; q=0.01

Referer: https://connectors.tableau.com/marketo/marketo/1/marketo.html

User-Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/538.1 (KHTML, like Gecko) tabprotosrv Safari/538.1

Accept-Language: en-us

Connection: Keep-Alive

Accept-Encoding: gzip, deflate

Host: *****.mktorest.com

RESPONSE  A

HTTP/1.1 200 OK

Server: nginx

Date: Fri, 10 Feb 2017 17:01:19 GMT

Content-Type: application/json;charset=UTF-8

Connection: keep-alive

Vary: Accept-Encoding

Content-Length: 18677

{

    "requestId": "****",

    "result": [**** 33 rows],

    "success": true,

    "nextPageToken": "MHFDCYN5AZMK5QHZ5P7FM4SNFEGXBMPOH4ZSTDGCS7Y72K5YZAPQ====",

    "moreResult": true

}

where the first record "activityDate" property is "2016-05-23T13:35:47Z" and the 33rd is "2016-06-13T15:15:19Z"

REQUEST B

GET https://***.mktorest.com/rest/v1/activities.json?nextPageToken=MHFDCYN5AZMK5QHZ5P7FM4SNFH6AI2UQM6LEY... HTTP/1.1

Accept: application/json, text/javascript, */*; q=0.01

Referer: https://connectors.tableau.com/marketo/marketo/1/marketo.html

User-Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/538.1 (KHTML, like Gecko) tabprotosrv Safari/538.1

Accept-Language: en-us

Connection: Keep-Alive

Accept-Encoding: gzip, deflate

Host: ***.mktorest.com

RESPONSE B

HTTP/1.1 200 OK

Server: nginx

Date: Fri, 10 Feb 2017 17:34:44 GMT

Content-Type: application/json;charset=UTF-8

Connection: keep-alive

Vary: Accept-Encoding

Content-Length: 166823

{

    "requestId": "***",

    "result": [**** 300 rows],

    "success": true,

    "nextPageToken": "MHFDCYN5AZMK5QHZ5P7FM4SNFFYODCNFHFGYO2W2EBLSWVB3JMYA====",

    "moreResult": true

}

where the first record "activityDate" property is "2016-05-23T13:35:47Z" and the 33rd is "2016-06-13T15:15:19Z" ( same as the former response, but it also contains 267 more rows, where row 34 "activityDate" property is "2016-06-19T12:36:11Z" and the last one is "2016-08-01T13:47:49Z"

5 REPLIES 5
Highlighted
Level 10 - Champion Alumni

Re: API, same request for activities endpoint having 2 different responses (for old data)

You may want to ask Support at either firm.

Highlighted
Anonymous
Not applicable

Re: API, same request for activities endpoint having 2 different responses (for old data)

Hi Josh Hill, could you elaborate what you mean for "Support at either firm"? and who can I specifically contact on Marketo's side for this?

Highlighted
Level 10 - Community Moderator

Re: API, same request for activities endpoint having 2 different responses (for old data)

Consider lead promotion.

Highlighted
Anonymous
Not applicable

Re: API, same request for activities endpoint having 2 different responses (for old data)

Hi Sanford Whiteman , could you elaborate this answer? I'm not sure I'm understanding

Highlighted
Level 10 - Community Moderator

Re: API, same request for activities endpoint having 2 different responses (for old data)

Web session promotion from Anonymous to Known.