Missing Data

Financial data availability varies by symbol, exchange, asset type, market state, and upstream coverage. gfin preserves unavailable values instead of inventing replacements.

Common Cases

• Search can return an empty result list for ambiguous or unsupported input.
• Quote views can omit fields for symbols where the dataset is unavailable.
• Realtime routes can require entity IDs instead of plain tickers.
• Some route families may return empty payloads during market closures or source availability gaps.

Application Guidance

• Treat missing optional fields as unavailable, not as zero.
• Show empty states for no search results or unavailable datasets.
• Keep the original meta.request_id when reporting a problem.
• Validate symbols with search before asking for multiple quote views.
• Branch on error.code for request failures.

Invalid Requests

Malformed requests return structured errors. For example, research without a query returns:

{
  "error": {
    "code": "bad_request",
    "message": "research requires q=, query=, or term=.",
    "next_action": "fix_request",
    "request_id": "..."
  }
}