Enterprise · API Reference

Intelligence API

Programmatic access to privacy-preserving, aggregate hiring signals. The API is designed for Enterprise integrations; candidate session and public recruiter routes use separate authorization contracts.

Authentication

Use an API key

Every Intelligence API request requires an active sk-iv-* Bearer key whose stored scopes and assigned tier both include intelligence:read. API-key management is currently available to Enterprise accounts from Settings → API.

Request headers

Authorization: Bearer sk-iv-your-api-key
Accept: application/json

Response contract

Consistent, traceable payloads

Successful response

{
  "data": {},
  "meta": {
    "request_id": "uuid",
    "timestamp": "2026-07-26T00:00:00.000Z",
    "rate_limit_remaining": 99
  }
}

Rate limiting

Per-key limit: configured rate_limit_rpm
New key default: 100 requests/minute

429 responses include Retry-After: 60.
Monthly quota checks fail closed if they
cannot be verified safely.

Error response

{
  "error": {
    "code": "bad_request",
    "message": "..."
  },
  "meta": {
    "request_id": "uuid",
    "timestamp": "2026-07-26T00:00:00.000Z"
  }
}

Endpoints

One aggregate surface

Method	Path	Returns	Query
GET	`/api/v1/intelligence/status`	API version, scopes, and endpoint inventory	—
GET	`/api/v1/intelligence/companies`	Aggregate company signals	limit, cursor, min_sample_size
GET	`/api/v1/intelligence/companies/trending`	Up to 20 recently active companies	—
GET	`/api/v1/intelligence/companies/{name}`	Detailed company aggregate	—
GET	`/api/v1/intelligence/companies/{name}/topics`	Ranked company topics	—
GET	`/api/v1/intelligence/companies/{name}/recruiters`	Company-level recruiter quality aggregate	—
GET	`/api/v1/intelligence/compensation`	Salary and equity percentiles	role_title required; location, remote_ok, company_stage
GET	`/api/v1/intelligence/market/snapshot`	Platform-wide aggregate snapshot	—
GET	`/api/v1/intelligence/recruiters/quality`	Company-level recruiter-quality aggregate	limit, cursor
GET	`/api/v1/intelligence/roles/demand`	Directional inbound demand signals	limit, cursor

The roles/demand endpoint currently derives directional signals from normalized company activity. Its role_title field therefore contains that current aggregate label.

Pagination

Pass every returned cursor back verbatim. The recruiter-quality and demand cursors are opaque ranking cursors, not names or offsets; do not construct, decode, or alphabetically increment them.

Privacy floors

Company lists, detail, topics, trending results, and snapshots need ten contributing candidates; compensation needs five matching signals; recruiter-quality data needs three recruiters and ten aggregate interactions; and demand data needs ten consenting candidate contributors in its 30-day cohort. Its trend is `null` until the prior cohort meets the same floor. Data below a threshold returns no aggregate.

Enterprise access

Connect Intraview to your hiring workflow

Enterprise plans include Intelligence API access and supported integration paths. Contact sales to discuss your environment and use case.

Contact Sales