Skip to main content
GET
Get Delivery Detail
Retrieve the full detail of a specific delivery, including the generated briefing content. The content is Markdown for most briefings, but may be HTML for certain briefing types. Use the delivery ID to retrieve citation sources via Get Delivery References.

Run trace

Add ?include_trace=true to also receive trace, which shows what the run was given and what the agent did:
  • context — the inputs: date range and news window, timezone, frequency, output language, tickers and company names, universe and ticker-selection context, excluded categories, preferred depth, enabled search sources, Outlook connection, whether the previous briefing was included (and its previous_delivery_id), the model, and the memory files loaded at session start (the owner’s memory in full, organization memory as its headings only).
  • steps — the agent’s thinking, narration and tool calls in execution order, each tool call with its input, result and error flag. The attribution validator’s verdict appears as the result of its Agent call.
trace is null while the delivery is still pending. Linq-internal material is withheld (reference docs, skill bodies, query text, sub-agent prompts, shell commands and what they or a search returned, written file bodies); a step with anything withheld carries redacted: true, and text cut at the length cap carries truncated: true. The trace makes the response considerably larger, so request it only when you need it.

Authorizations

X-API-KEY
string
header
required

Path Parameters

delivery_id
string
required

Query Parameters

include_trace
boolean
default:false

Also return trace: the context the run was given and the steps the agent took (see BriefingDeliveryTrace). Off by default because it makes the response considerably larger.

Response

200 - application/json

Delivery detail with content

error
object | null
payload
object