Not able to select Contacts table for syncing

SOLVE
Fivetran
Member

I tried to hit the following endpoint (Used for incremental sync):https://api.hubapi.com/contacts/v1/lists/recently_updated/contacts/recent

Response:

Fivetran_0-1606883312884.png

 

 

But when I tried to hit the Historical full sync endpoint for the same contacts table:
https://api.hubapi.com/contacts/v1/lists/all/contacts/all

 

Response :

Fivetran_1-1606883345864.png

 

 

 

For the same /contacts/ endpoint we are able to get response for 1 but not for another !!

I see that few other people using this endpoint are facing the problem where the recently_updated endpoint stopped working suddenly as shown here

NOTE: It's the same case for Deals and Companies endpoint

 @WendyGoh

 

 

 

 

0 Upvotes
1 Accepted solution

Accepted Solutions
dennisedson
Solution
Community Manager

Thanks!  Very strange... Are you using different access tokens?

Thanks,

Dennis




Check out our Community Developer Blog
where we feature our Community driven developer podcast and how to content

View solution in original post

0 Upvotes
5 Replies 5
dennisedson
Community Manager

Hey @Fivetran 
Could you update that link to the other post?  I am getting a 404

Thanks,

Dennis




Check out our Community Developer Blog
where we feature our Community driven developer podcast and how to content
0 Upvotes
Fivetran
Member
0 Upvotes
dennisedson
Solution
Community Manager

Thanks!  Very strange... Are you using different access tokens?

Thanks,

Dennis




Check out our Community Developer Blog
where we feature our Community driven developer podcast and how to content

View solution in original post

0 Upvotes
dennisedson
Community Manager

And without a word, my last potst was accepted as a solution.

@Fivetran was that the problem or are you just messing with me?

Thanks,

Dennis




Check out our Community Developer Blog
where we feature our Community driven developer podcast and how to content
0 Upvotes
Fivetran
Member

Hi @dennisedson , 

Our engineers informed me that the issue was somehow rectified on your side. Sorry, for the late response.