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

What is the API?

An API (application programming interface) is access for programs rather than people. Your SIEM, ticketing system or analytics tool queries eam.ch regularly and receives the data in a fixed format (JSON).

Like a mailbox from which your accounting software fetches the bank statements itself – instead of someone typing them in.

What it is good for

  • SIEM: see new findings alongside other security events and trigger alerts.
  • Ticketing system: reconcile open findings or tickets.
  • Analytics: show the grade and its trend in your own reports or dashboards.

The API delivers data on request. If messages should arrive as soon as something happens, webhooks are the better fit.

Secure and minimal

  • Read only – nothing can be changed via the API.
  • No personal data: no responsible persons, no external assignees.
  • One key per application. This lets you revoke one without affecting the others.

With eam.ch

  • In the customer area under Account → “Integrations” → “Manage API keys” (main users), create a key with a label.
  • Copy the key immediately and store it securely in your application – it is shown only once.
  • The application sends it with every request (see “For specialists”).
  • No longer needed or suspected misuse: revoke the key.

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).