From 841c7b4634006276a8a339e9579c747e86d502b2 Mon Sep 17 00:00:00 2001
From: Anton Burnashev <anton.burnashev@gmail.com>
Date: Fri, 24 May 2024 18:10:27 +0200
Subject: [PATCH] Mention JSONPath in resolve docs (#1409)

---
 docs/website/docs/dlt-ecosystem/verified-sources/rest_api.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/website/docs/dlt-ecosystem/verified-sources/rest_api.md b/docs/website/docs/dlt-ecosystem/verified-sources/rest_api.md
index 54edac5062..98725627b9 100644
--- a/docs/website/docs/dlt-ecosystem/verified-sources/rest_api.md
+++ b/docs/website/docs/dlt-ecosystem/verified-sources/rest_api.md
@@ -501,11 +501,13 @@ The syntax for the `resolve` field in parameter configuration is:
     "<parameter_name>": {
         "type": "resolve",
         "resource": "<parent_resource_name>",
-        "field": "<parent_resource_field_name>",
+        "field": "<parent_resource_field_name_or_jsonpath>",
     }
 }
 ```
 
+The `field` value can be specified as a [JSONPath](https://github.com/h2non/jsonpath-ng?tab=readme-ov-file#jsonpath-syntax) to select a nested field in the parent resource data. For example: `"field": "items[0].id"`.
+
 Under the hood, dlt handles this by using a [transformer resource](../../general-usage/resource.md#process-resources-with-dlttransformer).
 
 #### Include fields from the parent resource