easm.chUnderstanding your external attack surface

API: eam.ch data in SIEM, ticketing and analytics

Via the API, your own applications read the grade, findings, inventory, tickets and suppliers – automatically and without manual exports.

1 min read · in plain words and for experts

Diagram
  1. Your system
  2. Key, read-only
  3. Grade, findings, tickets
  4. Automatic analysis

Request

GET https://www.eam.ch/api.php?r=<resource> with header Authorization: Bearer eamk_…. JSON response with v (version 1), resource, generated_at (UTC) and tenant.

ResourceContent
ratingoverall grade and score, per category and per domain with last run
findingsfindings with ID, domain, category, check, severity, title, asset, status, timestamps and link; status=open (default) or all, lang=de|fr|it|en
assetsinventory: host names, addresses, services with first and last seen
ticketsnumber, title, domain, source, priority, status, due date, overdue, link
supplierssuppliers with grade, importance and check status
watchwatched domains with registration, mail, website, expiry and assessment

Examples

curl

curl -H "Authorization: Bearer eamk_…" "https://www.eam.ch/api.php?r=findings&status=open&lang=en"

PowerShell

$h = @{ Authorization = "Bearer $env:EAM_KEY" }
Invoke-RestMethod -Headers $h -Uri "https://www.eam.ch/api.php?r=rating"

Python

import os, requests
r = requests.get("https://www.eam.ch/api.php", params={"r": "tickets"},
                 headers={"Authorization": "Bearer " + os.environ["EAM_KEY"]}, timeout=30)
r.raise_for_status()
print(r.json()["tickets"])

Limits and errors

  • At most 120 requests per hour and key, at most 5 active keys per account. The data changes with the check runs – one request per hour is usually enough.
  • 401 key missing, wrong format or revoked · 403 account not active · 400 unknown resource · 405 GET only · 429 too many requests (header Retry-After).
  • Only the SHA-256 value of the key is stored; every request is recorded in the event log (SIEM, source “api”), creation and revocation in the account log.
  • Do not put the key in program code; keep it in an environment variable or a secrets vault.

Reference: ICT minimum standard DE.CM (continuous monitoring), ISO/IEC 27001:2022 A 8.16 (monitoring activities) and A 5.17 (authentication information).

In short

  • Via the API your applications read grade, findings, inventory, tickets, suppliers and watched domains.
  • Read only, no personal data, one key per application.
  • At most 120 requests per hour and key.
  • Keys under Account → Integrations → API keys (main users).

Check it yourself

Commands to verify on Linux or macOS. Replace ihre-domain.ch with your domain and only check your own systems.

curl -s -H 'Authorization: Bearer <schlüssel>' 'https://www.eam.ch/api.php/v1/findings?status=open'