# Last Execution Time of a Custom API

**URL:** <https://connective.celigo.com/t/last-execution-time-of-a-custom-api/4720>\
**Category:** API Management\
**Created:** [June 3, 2025, 1:31pm UTC](https://connective.celigo.com/t/last-execution-time-of-a-custom-api/4720 "2025-06-03T13:31:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SureshGarshakurthi](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/sureshgarshakurthi/32/7288_2.png) [@SureshGarshakurthi](https://connective.celigo.com/u/SureshGarshakurthi)\
**Post date:** [June 3, 2025, 1:31pm UTC](https://connective.celigo.com/t/last-execution-time-of-a-custom-api/4720/1 "2025-06-03T13:31:25Z")

</div>

Hey Celigo World,

A question about the Celigo's APIs.

We're building a custom API using **Celigo’s API Builder** and need to support delta-style exports using a `since_id` or timestamp-based filter. Does Celigo internally store a `LastExecutionTime` (or last successful run timestamp) for custom-built APIs\*\*, similar to how delta exports work in standard integrations?

Our goal is to implement logic that returns records **created or updated since the last successful execution** , so the API behaves incrementally rather than retrieving the full dataset each time.

I’m currently exploring a few alternative approaches but wanted to check if there’s a **built-in token** like `{{lastExportDateTime}}` available in the API Builder, or any best practices others have used to achieve this pattern.

Just brainstorming here — would appreciate any tips, examples, or things I might be overlooking!

---

<div class="post-metadata">

**Author:** ![kaustavroy](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/kaustavroy/32/6640_2.png) [@kaustavroy](https://connective.celigo.com/u/kaustavroy)\
**Post date:** [June 3, 2025, 2:44pm UTC](https://connective.celigo.com/t/last-execution-time-of-a-custom-api/4720/2 "2025-06-03T14:44:52Z")

</div>

Hi @SureshGarshakurthi

Thank you for the question. Since the custom APIs built using API builder are ideally stateless (unlike flows with delta exports), it is recommended to maintain the timestamp at consumer's end, and use it to fetch delta records. Hope this helps!

Thanks,  
Kaustav