Skip to main content
Retrieve filing-derived product or geography revenue disclosures for one issuer, including capability state and trace references when the issuer provides the underlying detail.
Audience: application and coding agent.

Coverage and source scope

Use this route to analyze revenue splits the issuer actually disclosed in XBRL. Choose annual or quarterly cadence and, when useful, narrow to a product, geographic, or other reported dimension. Records retain the reported unit, period, segment hierarchy, capability status, and filing provenance; they are not a modeled revenue allocation. Preserve the returned accession, filing URL, and freshness fields before aggregating or presenting the result. See API conventions and freshness and source evidence.

Disclosure-aware revenue history

Supply one issuer identifier. Use period and segment_type to narrow the requested product or geography history, and use limit, segment_limit, and submission_file_limit to bound the work performed and the response size. The response reflects filing-derived disclosures, not a modelled revenue allocation. Check capability state, trace references, provenance, freshness, and materialization before comparing issuers or treating an absent product/geography row as zero.

Business breakdown workflow

Build disclosure-aware product and geography views.

Freshness and trust

Keep source timing and provenance visible in downstream use.

Canonical metadata

  • requestId
  • traceparent
  • provenance
  • freshness
  • materialization

Example request

Example response

About this example

This response is illustrative: the issuer, accession, segment members, and example.com URL are synthetic. It aligns an annual geographic revenue record with the request and does not claim a live SEC filing.

Give this prompt to your agent

Failure posture

  • provide one issuer identifier and keep period and segment limits bounded for a predictable response
  • treat absent product or geography rows as undisclosed or unavailable, not as zero revenue
  • preserve capability state, trace references, provenance, freshness, materialization, requestId, and traceparent when handling a partial or transient result