You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/universal-connector-source.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ Invalid examples:
125
125
126
126
#### Request Headers
127
127
128
-
Include any HTTP request headers required by the vendor API. The key names are static text, but the values can access our [template feature](#template-dynamic-values) to make them dynamic.
128
+
Include any HTTP request headers required by the vendor API. The key names are static text, but the values can access our [variables feature](#dynamic-values) to make them dynamic.
@@ -135,7 +135,7 @@ Include any HTTP request headers required by the vendor API. The key names are s
135
135
136
136
#### Request Parameters
137
137
138
-
Include any URL query parameters required by the vendor API. The key names are static text, but the values can access our [template feature](#template-dynamic-values) to make them dynamic.
138
+
Include any URL query parameters required by the vendor API. The key names are static text, but the values can access our [varables feature](#dynamic-values) to make them dynamic.
This is optional and only used if the HTTP `POST` method is configured above. You can use this field to include any information in the HTTP request body. The data included in this field can access our [template feature](#template-dynamic-values).
151
+
This is optional and only used if the HTTP `POST` method is configured above. You can use this field to include any information in the HTTP request body. The data included in this field can access our [dynamic values](#dynamic-values).
152
152
153
153
</div>
154
154
</details>
@@ -159,9 +159,9 @@ This is optional and only used if the HTTP `POST` method is configured above. Yo
159
159
160
160
#### Time Window
161
161
162
-
The source will provide both a start and end timestamp for you to [dynamically](#template-dynamic-values) use in your HTTP request. The window will only move forward if no errors are raised when collecting logs from the vendor API for the current window.
162
+
The source will provide both a start and end timestamp for you to [dynamically](#dynamic-values) use in your HTTP request. The window will only move forward if no errors are raised when collecting logs from the vendor API for the current window.
163
163
164
-
Use the [template feature](#template-dynamic-values) to include the window start and end timestamps within your HTTP request.
164
+
Use the [dynamic values](#dynamic-values) to include the window start and end timestamps within your HTTP request.
165
165
166
166
The start time is inclusive and the end time is exclusive as that is the behavior of most APIs.
167
167
@@ -377,7 +377,7 @@ Sources can be configured using UTF-8 encoded JSON files with the Collector Ma
377
377
| clientRateLimitBurst | Integer | Yes |`1000`| The number of requests the source is allowed to burst. |`1000`|
378
378
| pollingInterval | String | Yes |`"5m"`| Set how frequently to poll for new data. It must be between 5 minutes and 48 hours. |`"5m"`|
379
379
380
-
## Dynamic Values Variables
380
+
## Dynamic Values
381
381
382
382
The source has the ability to use dynamic values, like the window start time, into the values of certain fields providing flexibility in crafting the HTTP requests sent to the vendor API.
0 commit comments