API and webhooks
786 Cyber works with the tools you already run, through open standards rather than custom connectors:
- Webhooks push events to your SIEM, SOAR or automation tool as they happen, signed with the Standard Webhooks spec, with findings in OCSF 1.3.0. Set them up in Settings › Integrations › Webhooks; the Team & settings page explains how.
- The API lets your scripts, BI tools and partner systems read your data whenever they need it. It is read-only and described in an OpenAPI 3.1 file you can load into Postman, Insomnia or a code generator.
Both are available when they are included for your organisation. Ask your 786 Cyber contact if you don’t see them under Settings › Integrations.
Create a key
Section titled “Create a key”- Go to Settings › Integrations › API keys (owners, admins and security leads).
- Click Create key, give it a name such as “Power BI”, choose what it can read, and pick when it expires.
- Copy the key. It starts
786_live_and is shown once; we keep only a fingerprint of it.
Send it with every request:
curl -H "Authorization: Bearer 786_live_…" https://786cyber.com/api/v1/meRevoke stops a key at once. Keep keys in your tool’s secret store, never in code; the fixed 786_live_ prefix helps secret scanners spot one that leaks.
What a key can read
Section titled “What a key can read”| Scope | Endpoints | What you get |
|---|---|---|
findings:read | /findings, /findings/{id} | Findings with severity, status, CVE, CVSS, EPSS, known-exploited flag, priority and asset |
assets:read | /assets, /assets/{id} | Devices, domains, cloud and software with status, criticality and risk |
scans:read | /scans | Scans and their results |
compliance:read | /assessments, /controls | Framework assessments with scores, and the status of each control |
evidence:read | /evidence | Evidence titles, types, tags and expiry dates; never the files or file names |
risks:read | /risks, /risks/{id} | The risk register with inherent and residual scores |
events:read | /events | The same events webhooks send, for tools that poll instead |
people:read | /people | Names, work emails and identity posture (MFA, admin rights, last sign-in). Not ticked by default |
/me needs no scope: it tells you which organisation and key you are using.
Paging and keeping in sync
Section titled “Paging and keeping in sync”Lists return the oldest change first:
{ "data": [ … ], "next_cursor": "eyJ0Ijoi…" }Pass next_cursor back as cursor until it comes back null. limit sets the page size (default 100, up to 500). To keep a copy in sync, remember the last updated_at you saw and next time ask for updated_since=<that time>.
/findings also takes status (open, in_progress, awaiting_verification, pending_approval, exception, closed), severity and asset_id; /assets takes type; /events takes type, a comma-separated list such as finding.created,scan.failed. Events are kept for 30 days.
Limits and errors
Section titled “Limits and errors”Each key can make up to 600 requests a minute, and each organisation 1,200. Over that you get 429 with a Retry-After header. Errors look like this:
{ "error": { "code": "missing_scope", "message": "This key does not have the assets:read scope." } }| Status | Meaning |
|---|---|
| 400 | A parameter isn’t valid |
| 401 | No key, or the key is unknown, revoked or expired |
| 403 | The key lacks the scope, or the API isn’t included for your organisation |
| 404 | Not found in your organisation |
| 405 | The API is read-only: use GET |
| 429 | Too many requests |
Your organisation always comes from the key, so one key can only ever read its own organisation’s data. Every call is counted per key, and Last used in Settings shows when each key was last used.
Send webhooks to Elastic
Section titled “Send webhooks to Elastic”Events can go straight into Elasticsearch (self-managed or Elastic Cloud) with no collector in between: each event becomes one document. Tested against Elasticsearch 9.5.
1. Set up the index once. In Kibana › Dev Tools, as a user who can manage indices, run these two requests. The first copies each event’s time into @timestamp, which Discover and Elastic Security expect. The second stores the OCSF times (milliseconds since 1970, in fields such as data.finding_info.created_time) as dates rather than numbers.
PUT _ingest/pipeline/786-events{ "description": "786 Cyber webhooks: copy the event time into @timestamp", "processors": [ { "set": { "field": "@timestamp", "copy_from": "timestamp", "ignore_empty_value": true } } ]}
PUT _index_template/786-events{ "index_patterns": ["786-events*"], "priority": 200, "template": { "settings": { "index.default_pipeline": "786-events" }, "mappings": { "dynamic_templates": [ { "ocsf_times": { "match_mapping_type": "long", "match_pattern": "regex", "match": "^(time|.*_time)$", "mapping": { "type": "date", "format": "epoch_millis" } } } ], "properties": { "@timestamp": { "type": "date" }, "timestamp": { "type": "date" }, "id": { "type": "keyword" }, "type": { "type": "keyword" }, "schema_version": { "type": "keyword" }, "org": { "properties": { "id": { "type": "keyword" } } } } } }}2. Create a key that can only add events. Still in Dev Tools:
POST /_security/api_key{ "name": "786-cyber-webhooks", "role_descriptors": { "webhook_writer": { "indices": [ { "names": ["786-events*"], "privileges": ["create_doc", "auto_configure"] } ] } }}Copy the encoded value from the reply. This key can add documents to 786-events and nothing else: it can’t read, change or delete anything.
3. Add the endpoint. In Settings › Integrations › Webhooks, choose Add endpoint and pick Elastic as the receiver. Enter your Elasticsearch address (for example https://elastic.example.com or your Elastic Cloud endpoint) and paste the encoded key. We send to /786-events/_doc with the header Authorization: ApiKey <encoded key>. Click Send test event: you should see “Test event delivered (HTTP 201 …)”.
4. Look at your events. In Kibana › Stack Management › Data views, create a data view for 786-events* with @timestamp as the time field, then open Discover. Each event’s type says what happened (for example scan.completed or finding.created), and findings carry the OCSF fields (class_uid, severity, status, finding_info) under data, ready for searches, dashboards and detection rules.
Your Elasticsearch must be reachable over HTTPS from the internet, with a certificate from a public authority; we don’t follow redirects. If you set up the endpoint before the index template, the first fields are already fixed: copy the index aside with _reindex, delete it, and copy it back with "pipeline": "786-events".