Get v1 events voting results

GET /v1/events/voting-results

Return 8-K Item 5.07 voting results with structured proposals, vote counts, and approval outcomes — first-in-market parser ahead of sec-api.io’s open bug

Audience: application and coding agent.

Agent mode

Pass ?view=agent to receive the compact agent shape: event identifiers (ticker, form, filingDate, accessionNumber, meetingDate, meetingType, headline) + lifted filingUrl + nested proposals[] trimmed to 7 fields per proposal (number, description, proposalType, votesFor, votesAgainst, abstain, approved). brokerNonVotes, voteFormat, summaryMd, parser version, superseded flag, and metadata envelopes are dropped. Typical reduction: ~85%. See api conventions → response formats for the full ?view= contract.

Canonical metadata

• requestId
• traceparent

Example request

curl -X GET \
  -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  -H "omni-version: 2026-03-19" \
  "https://api.secapi.ai/v1/events/voting-results?ticker=AAPL"

Example response

{
  "requestId": "req_example_123",
  "traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}

Give this prompt to your agent

CopiedCopy prompt

Failure posture

• treat non-2xx responses as contract-aware failures, not free-form errors
• preserve requestId and traceparent in logs and downstream reports
• if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff