:censored: pagingToken | Community
Skip to main content
Level 2
August 9, 2024
Solved

:censored: pagingToken

  • August 9, 2024
  • 1 reply
  • 1460 views

Hi,

 

So I'm trying to GET the pagingToken to later fetch some email reports. I need the pageToken for this but it will only give out a ":censored:" Next Page Token.

 

These are my fields:

URL: localhost/rest/v1/activities/pagingtoken.json (annonymizing my address)

 

Query String Parameters: sinceDatetime=2024-04-12T12:00:00Z

 

Response would be:

{"requestId":"3e6e#29236e43b3a","success":true,"nextPageToken":":censored:65:2d0ad1a30b:"} (some data have been changed for privacy reasons)
 
Is there anything I'm missing? I've also tried to put the access token as a form of authentication but keeps "censoring" my Next Page Token 😞
 
Thanks!

 

Best answer by SanfordWhiteman
Marketo isn't censoring, it's Zapier. Lots of discussion here: https://www.google.com/search?q=zapier+censoring+js+responses

1 reply

SanfordWhiteman
Level 10
August 10, 2024
What client app or library are you using to make this request?
ChaloAuthor
Level 2
August 12, 2024

I'm using Zapier 🙂

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
August 12, 2024
Marketo isn't censoring, it's Zapier. Lots of discussion here: https://www.google.com/search?q=zapier+censoring+js+responses