From 0e2df68fcc9e90823fd6a3dedad002da1e9f7404 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Edgar=20Ram=C3=ADrez=20Mondrag=C3=B3n?=
 <16805946+edgarrmondragon@users.noreply.github.com>
Date: Tue, 27 Aug 2024 20:09:25 -0600
Subject: [PATCH] docs: Reference `get_starting_timestamp` in incremental
 replication guide (#2629)

* docs: Reference `get_starting_timestamp` in incremental replication guide

* Use correct paren

* Add comma
---
 docs/incremental_replication.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/incremental_replication.md b/docs/incremental_replication.md
index 757f15802..085f20afc 100644
--- a/docs/incremental_replication.md
+++ b/docs/incremental_replication.md
@@ -38,6 +38,7 @@ class CommentsStream(RESTStream):
 
 3. Last, we have to adapt the query to the remote system, in this example by adding a query parameter with the ISO timestamp.
 
+   The [`get_starting_timestamp`](singer_sdk.Stream.get_starting_timestamp) method and the related [`get_starting_replication_key_value`](singer_sdk.Stream.get_starting_replication_key_value) method, are provided by the SDK and return the last replication key value seen in the previous run. If the tap is run for the first time and the value for the `start_date` setting is null, the method will return `None`.
 
 ```{note}
 - The SDK will throw an error if records come out of order when `is_sorted` is true.