registercheckby openlaw group
API referenceMonitoring

List monitor event types

GET
/monitor-event-types

Every event type a monitor can subscribe to, what to call it, and whether it works.

Read available before offering a choice. Some event types are published so that a monitor created with them is not rejected, but produce nothing today — a source that is built and not switched on, or one nothing schedules. unavailable_reason says which.

unavailable_groups lists categories the product shows that this API cannot serve at all, so a client can render every category from one list instead of hard-coding them.

The same for every caller, and it reads no account data — but it needs an API key, like every operation but /health.

Free.

Authorization

bearerAuth
AuthorizationBearer <token>

Your API key, sent as Authorization: Bearer rc_live_….

In: header

Response Body

application/json

application/problem+json

application/problem+json

curl -X GET "https://api.registercheck.de/v1/monitor-event-types" \  -H "Authorization: Bearer $REGISTERCHECK_API_KEY"
{  "object": "list",  "data": [    {      "id": "*",      "object": "monitor_event_type",      "label": "string",      "label_de": "string",      "group": "string",      "group_label": "string",      "group_label_de": "string",      "available": true,      "unavailable_reason": "string"    }  ],  "unavailable_groups": [    {      "object": "monitor_event_group_gap",      "group": "string",      "group_label": "string",      "group_label_de": "string",      "reason": "string"    }  ]}