DEVELOPERS

API‑first is not a slogan

Integrations are designed as part of the product: predictable resources, events, webhooks and a clear versioning model.

API PREVIEW

Target integration model

The example below shows the target 34.12 Surface API shape. It is a website interface specification, not a claim that a production endpoint is already available.

surface-api.txt

GET /v1/assets?risk=high
Authorization: Bearer <token>

{
  "items": [
    {
      "id": "ast_3412",
      "type": "domain",
      "value": "api.company.example",
      "risk": "high",
      "exposures": 3
    }
  ],
  "next_cursor": null
}

REST / EVENTS

Resource-oriented API plus events for asynchronous workflows.

VERSIONING

Explicit API versions and backwards-compatible changes.

WEBHOOKS

Event delivery for asset and exposure changes.

AUTH

Token-based access with future enterprise identity options.

EXPORT

Machine-readable data for SIEM, SOAR, ITSM and data platforms.

DOCS

Examples, schemas and changelog published together with releases.

Need an integration?

Tell us the target system and data flow.

Discuss