Skip to main content

​
GET /v1/filings//similar

Find filings with semantically similar content to a given filing.
Audience: application and coding agent.

​
Parameters

ParameterTypeRequiredDescription
filingIdstringYesFiling identifier used as the semantic similarity source
limitintegerNoMaximum results to return (1-20, default: 5)
formstringNoOptional form filter such as 10-K, 10-Q, or 8-K

​
Canonical metadata

  • requestId
  • traceparent
  • Omni-Meter-Class: semantic_search billing header

​
Example request

curl -X GET \
  -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  -H "omni-version: 2026-03-19" \
  "https://api.secapi.ai/v1/filings/0000320193-25-000079/similar?limit=5&form=10-K"

​
Example response

{
  "object": "similar_filings",
  "sourceFilingId": "0000320193-25-000079",
  "requestId": "req_example_123",
  "traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01",
  "results": {
    "object": "list",
    "data": [
      {
        "filingId": "0000789019-25-000014",
        "ticker": "MSFT",
        "form": "10-K",
        "filingDate": "2025-07-30"
      }
    ],
    "count": 1
  }
}

​
Give this prompt to your agent

​
Failure posture

  • treat non-2xx responses as contract-aware failures, not free-form errors
  • preserve requestId and traceparent in logs and downstream reports
  • preserve Omni-Meter-Class when present so downstream billing and usage reasoning stays intact, even if it is carried as header metadata rather than payload data
  • expect one result per unique filing because the endpoint deduplicates by filing ID
  • treat the source filing embedding as derived retrieval context built from the source filing’s top sections rather than a user-visible artifact