Argusdocs

API access

Licensed programmatic access to the tracked corpus: the same dated, receipted observations the terminal shows, served as JSON over versioned read-only endpoints.

Connected Source

For the externally executed research workflow, use the separate Source tool reference. The v1 API described here remains the licensed Argus market-data reader.

What the API serves

Every response is assembled from observed data. A row is something Argus saw on a real page on a real date, and it carries its receipt: the source address, the observation date, and the verification state. Where the corpus has nothing on file, the API says so instead of filling the gap.

  • Signals. The dated change stream: sponsors appearing, dropping, changing tier.
  • Events. The roster ledger and per-event profiles with edition history.
  • Companies. A company's observed sponsorship record across the catalog.
  • Coverage. How deep the corpus is, so you can judge what absence means.
  • Buying window. The lapsed-but-active-elsewhere lens, receipts behind every cell.
  • Movers. Entrant cohorts per event edition, sliced by geography and kind.

What the API deliberately does not serve

  • No scores or rankings. No propensity numbers, no fit ranks, no bands. Ranked target work for your own event is the Operating System, a separate seat product.
  • No estimates. Modeled figures shown in the app (like fee estimates) are excluded. The API serves observed facts only.
  • No bulk export. Every list endpoint is paginated with a hard page cap. There is no endpoint that returns the whole catalog in one response.
  • No contributed data. Data a customer contributes under an agreement never flows to other customers through this API.

Getting access

API access is an add-on to an Argus licence, scoped to what the licence covers: one or more verticals, or the full catalog. An admin of your organisation creates and manages keys from the Organisation tab in Settings. See Authentication and keys for the key lifecycle and Scopes, limits, usage for what a scope covers.

Versioning

The current version is v1, under the /api/v1/ path. v1 is additive: fields may be added over time, and existing fields keep their meaning. A breaking change would ship as a new version namespace with a dated deprecation note here, never as a silent edit.