Skip to main content

​
GET /v1/events/voting-results

Return 8-K Item 5.07 voting results with structured proposals, vote counts, and approval outcomes.
Use this endpoint from server-side applications, SDKs, or agent workflows.

​
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.

​
Response metadata

  • requestId
  • traceparent

​
Example request

curl -X GET \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-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

Copy this SEC API prompt for your agent.

​
Errors and partial results

  • Treat non-2xx responses as API errors and log the response body for debugging
  • Log requestId and traceparent so SEC API support can trace the request
  • if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff