Skip to content

Commit 76dd739

Browse files
committed
JETS-382: Add external_call_unique_id callouts to signal api doc
1 parent 3bb8f68 commit 76dd739

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

source/api_documentation/signal_api/index.rst

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@ Used to find the call associated with the signal.
5858

5959
or
6060

61+
`external_call_unique_id` The unique ID of the call from an external system.
62+
63+
or
64+
6165
`call_start_time` The start time does not have to be exact since clocks will not be perfectly synchronized. We will find the closest match (in combination with **duration_in_seconds**, if provided). See **Timestamp Formats** section below for descriptions of supported timestamps.
6266

6367
Note: If using **call_start_time** to match, instead of **transaction_id**, one or more of the following optional parameters is highly recommended. The optional parameters are ignored when using the **transaction_id**:
@@ -225,7 +229,7 @@ For example, if a **transaction_id** or **call_start_time** are not passed in th
225229
{
226230
"errors": {
227231
"class": "InvalidInput",
228-
"invalid_data": "transaction_id, call_record_id, or call_start_time must not be empty"
232+
"invalid_data": "transaction_id, call_record_id, external_call_unique_id, or call_start_time must not be empty"
229233
}
230234
}
231235

0 commit comments

Comments
 (0)