List the Accepted Research Detail Types
Returns each research detail type and the rules for writing a value of that type. The rules include valueShape, allowedToken, range, and timeSeries. When timeSeries=true, each believable dated observation is historical data: add a new current row and delete only rows believed false.
Authentication
Your aVenture API key (https://aventure.vc/settings/api-keys) or OAuth access token
Response headers
Requests allowed per client IP in the current rate-limit window.
Requests left before the tightest applicable rate-limit bucket rejects.
Seconds until the exhausted rate-limit bucket admits another request; 0 when none is exhausted.
Response
Whether rows are dated history; true means add current observations and keep believable old rows.
Write-time value shape token. For numericCountOrRange details, send either discreteValue for an exact count or textValue for an employee range.
Value kind on reads; pick write fields from valueShape.
How to encode a write for this valueShape: which of valueResearchDetail, discreteValue, textValue, and asOfDate to send, with an example.
Effective concrete entity kinds for this detail, including inherited section applicability; absent only on older servers. Path prefixes do not override this leaf rule.
Inclusive numeric bounds for monetary and numericRatio, numericScore, and numericGrowthRate values. numericGrowthRate uses percentage points: 80 means 80%, not 0.8.