Signals
Get Signal
Retrieve a signal’s full flat list of verified units
GET
Unique signal identifier (e.g.,
0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7).title, url, and published_at always describe the full source. The units below 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.Unique signal identifier.
Source title. Describes the full source, not necessarily the extracted segment.
Source URL. Links to the full source.
ISO 8601 publication date of the full source.
analysis or event.Source registrable domain (e.g.
reuters.com).Number of verified units; equals the length of
units. The honest depth signal; use it, not statement length, to gauge analytical depth.Themes with
value_chain and market_force arrays.Entities mentioned in this signal (
entity_id, name, type).Flat list of verified units, grouped by role (central statement → arguments → claims) in document order. List position is the order; there is no separate index field.
Authorizations
API key for authentication. Include in every request as X-API-Key: gld_your_key_here.
Path Parameters
Response
Successful Response
Full signal as a flat list of verified units (grouped by role, in document order).
Example:
"0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7"
Publication timestamp (ISO 8601).
Available options:
analysis, event Example:
"analysis"
Source registrable domain.
Example:
"reuters.com"
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.