> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/events/voting-results

> Retrieve structured shareholder-vote results from 8-K Item 5.07 filings

Retrieve structured shareholder-vote results from 8-K Item 5.07 filings

<Info>
  Audience: application and coding agent.
</Info>

## Coverage and source scope

Returns proposals, vote counts, and reported outcomes extracted from 8-K Item 5.07 disclosures for one issuer. It is not a universal proxy-voting archive: issuer identity is required, coverage is limited to eligible filings scanned, and proposal interpretation should retain the cited accession and source fields. Treat filing dates as disclosure dates and continue with the returned `nextCursor` value for the same filters. See [API conventions](https://docs.secapi.ai/api-conventions).

## Agent mode

Pass `?view=agent` to receive the compact agent shape: event identifiers (ticker, form, filing date, accession number, meeting date, meeting type, and headline), the cited filing URL, and a compact proposal list. Vote-format detail, parser metadata, and the longer summary are omitted. See [api conventions → response formats](/api-conventions) for the full `?view=` contract.

## Canonical metadata

* `requestId`
* `traceparent`
* `per-row provenance`
* `per-row freshness`
* `per-row materialization`

## Example request

<RequestExample>
  ```bash theme={null}
  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"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "list",
    "data": [],
    "hasMore": false,
    "nextCursor": null,
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/events/voting-results to retrieve structured shareholder-vote results from 8-K Item 5.07 filings. Preserve `requestId`, `traceparent`, `per-row provenance`, `per-row freshness`, `per-row materialization` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</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