Skip to main content
Question

Sync API does not pull changes to data

D
Active

Hi,

 

I have been trying to use the sync API to try and pull changes from a data model - specifically node instances from a view. When testing, some fields within a view was changed / updated but I was not able to pull anything new using the sync API. This was after I created a baseline of the full dataset using the Query endpoint.

The sync endpoint did work when new nodes were added to the view, it would only pull the new row, so I think my query is correct. Is there some sort of parameter to turn on / other way to use the sync API to retrieve changes and new additions to instances?

2 replies

Arild Eide
Seasoned Practitioner
Forum|alt.badge.img
  • Arild Eide
  • Seasoned Practitioner
  • 40 replies
  • April 2, 2025

Hi ​@duncan.murray 

 

I think the sync endpoint will return both instances that have been created and mutated since the previous call to sync, provided the request includes the cursor returned in the previous call and the instances still satisfy the filter in the request.

There is a general description of the sync endpoint and how it differs from the query endpoint in the documentation as well as an example available in the Python SDK documentation.

 

Hope this helps

 

Arild Eide

D
Active
Arild Eide wrote:

Hi ​@duncan.murray 

 

I think the sync endpoint will return both instances that have been created and mutated since the previous call to sync, provided the request includes the cursor returned in the previous call and the instances still satisfy the filter in the request.

There is a general description of the sync endpoint and how it differs from the query endpoint in the documentation as well as an example available in the Python SDK documentation.

 

Hope this helps

 

Arild Eide

Yes this is exactly what I’m expecting but when data mutates/changes in the source, I am not able to pull it at all - I get nothing back from the sync with the cursor used from the last full load query. From what I’m reading in the documentation this seems like a bug. 

Reply


Terms & ConditionsCookie Settings

Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings