Record the SEC API version you use

​

Prerequisites

• An API key in SECAPI_API_KEY.
• A known working endpoint.

​

Send and inspect the version

curl --include --fail-with-body \
  "https://api.secapi.ai/v1/entities/resolve?ticker=AAPL" \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-version: 2026-03-19"

Request-Id: req_...
SECAPI-Version: 2026-03-19

​

Use it in a client

import { SecApiClient } from "@secapi/sdk-js"

const sec = new SecApiClient({
  apiKey: process.env.SECAPI_API_KEY,
  apiVersion: "2026-03-19",
})

const issuer = await sec.resolveEntity({ ticker: "AAPL" })
console.log(issuer.ticker)

​

When something changes

1. Reproduce the request with the same method, path, parameters, and response view.
2. Capture Request-Id, SECAPI-Version, status, and the error code when present.
3. Compare the affected operation’s API reference and the changelog.
4. Test any new client or application version in a controlled environment before moving production traffic.

​

Limits and production notes

• A version header does not make an undocumented field or endpoint-specific projection universal.
• Treat new optional fields and unknown enum values defensively.
• Keep version configuration near your client construction and log the response version with each failed request.
• Do not infer a release policy from an echoed header; use published migration guidance when it exists.