Hello, I just tested the Data Extract API that seems very useful for reporting purpose. I have one question about the most appropriate way of using this feature. I have a 5 m objects object class that I want to use in my reporting. Data will be stored in a DW. This 5m rows table is only containing data can not be modified or deleted once created. Today, to transfert the data from Appfarm to the DW, i’m using graphQL and filter on the af_createdDate. I really like how hast and how easy is it with the Data Extract API, but how can it be possible to know the cursor if I want to load only the data that was created from Example: Today, I’m loading the entire data set: no problem with the Data Extract API Tomorrow: I only want to add the data created during the day: what’s the best way to achieve this ? reload the entire data set ?

Hi! Have you tried using the ID of the last returned object as the cursor in your next request? In theory, the object IDs are automatically increasing, meaning that if you use the ID of the last object from yesterday in your request today, you should only receive objects created since your last request. The data is not necessarily ordered on createdDate, but all the object should be created after your previous cursor. I hope that works; if not, please let us know.

I was thinking about it, but when using the last ID (last of day one) as the start cursor for the next day (day two) I’ve this specific record loaded twice. But I can also handle it by removing the duplicates

Hi @Lars, Using the data extract API for a couple of months now, it would be super great to have an additionnal param to “exclude cursor”. Today, I have a logic that runs every day. On day D, i’m using the last id of D-1 as next cursor (because on D-1, i dont have any “next cursor” as i’m at the end of the table), but I need to remove this specific line to append in the datawarehouse, otherwise it appears twice. So, querying the data extract api with: next_cursor = my_next_cursor_id, exclude_cursor = true would be very useful in that situation. #feature-requests

Hi, Jeremy! Thank you for providing a clear description of the issue you’re facing. I can see how an ‘exclude_cursor’ query parameter could be beneficial in this situation. I’ll register this as a feature request internally.

Hi! The feature Data Export Endpoint - New query param: exclude_cursor has now been given priority. It is currently scheduled for introduction in release 115. Please note that this is subject to change. Thanks!

Great, thanks a lot, it’ll make the process smoother

Perfect ! thanks a lot :slight_smile:

Delta load using Data Extract API

Ask the community

Olav March 21, 2025, 7:03am 8

Hello! This feature is now live in version 115.

Topic		Replies	Views
Introducing Data Extract API Announcements product-update	0	142	September 26, 2024
Export database/everything Ask the community app-data , actions	1	393	June 14, 2023
Enum Data Extract Ask the community service	3	108	October 14, 2026
Release Notes 115 Release notifications	0	76	March 20, 2025
Sending all app data to Open AI Ask the community	21	360	May 30, 2025

Delta load using Data Extract API

Related topics