Get Signal
Retrieve a signal’s full flat list of verified units
title, url, and published_at always describe the full source. The units may reflect only a segment of that source (e.g., a five-minute exchange in a two-hour podcast). See Signal scope vs. source scope.Authorizations
API key for authentication. Include in every request as X-API-Key: gld_your_key_here.
Path Parameters
Unique signal identifier.
"0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7"
Response
Successful Response
Full signal as a flat list of verified units (grouped by role, in document order).
"0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7"
"https://reuters.com/technology/nvidia-h200-shipments"
Number of verified units in the decomposition (equals len(units) in detail). The honest depth signal — use this, not statement length, to gauge analytical depth.
12
"NVIDIA H200 Shipments Surge as Supply Eases"
Publication timestamp (ISO 8601).
"2026-01-15T10:00:00Z"
analysis, event "analysis"
Source registrable domain.
"reuters.com"
Flat list of verified units, grouped by role (central statement, then arguments, then claims) in document order. List position is the order; there is no separate index field.