How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Events.com Alert History API

APIs for managing alert execution history

Events.com Alert History API is one of 113 APIs that Events.com publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Alert History. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 9 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://datagol-be.events.com.

9 operations 8 paths 10 schemas 2 DELETE7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://datagol-be.events.com/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Events.com Alert History API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (s_jwt).

  • s_jwt — Jwt Token

Paths & Operations 9

Across 8 paths, the API surfaces 9 operations — 2 DELETE, 7 GET. Each is listed below with its method, path, parameters, and response codes.

Alert History 9

APIs for managing alert execution history

GET
/alerts/history/api/v1/statistics
Get alert statistics for company
getAlertStatistics 1 param → 400503403501500200
GET
/alerts/history/api/v1/company
Get alert history for company
getCompanyAlertHistory → 400503403501500200
GET
/alerts/history/api/v1/company/paginated
Get paginated alert history for company
getCompanyAlertHistoryPaginated 1 param → 400503403501500200
GET
/alerts/history/api/v1/company/count/triggered
Count triggered alerts for company
countCompanyTriggeredAlerts → 400503403501500200
GET
/alerts/history/api/v1/alert/{alertId}
Get alert history for a specific alert
getAlertHistory 1 param → 400503403501500200
DELETE
/alerts/history/api/v1/alert/{alertId}
Delete alert history for specific alert
deleteAlertHistory 1 param → 400503403501500200
GET
/alerts/history/api/v1/alert/{alertId}/triggered
Get triggered alerts for a specific alert
getTriggeredAlerts 1 param → 400503403501500200
GET
/alerts/history/api/v1/alert/{alertId}/paginated
Get paginated alert history for a specific alert
getAlertHistoryPaginated 2 params → 400503403501500200
DELETE
/alerts/history/api/v1/cleanup
Clean up old alert history
cleanupOldAlertHistory 1 param → 400503403501500200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are UserDTO (21 properties), AlertHistoryDTO (18 properties), AlertExecutionMetadata (14 properties), PageAlertHistoryDTO (11 properties). Each schema is shown below with its type and property counts.

TupleStringMapStringObject
object
2 properties
AlertHistoryDTO
object
18 properties
AlertExecutionMetadata
object
14 properties
PageAlertHistoryDTO
object
11 properties
Pageable
object
3 properties
PageableObject
object
6 properties
UserDTO
object
21 properties
SaasxlResponseDTOObject
object
5 properties
ErrorMessage
object
5 properties
SortObject
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eventscom-alert-history-api-openapi.yml Raw ↑

Other APIs Events.com publishes across the network.

DataGol MCP Server
Events.com Agent Config Controller API
Events.com Agent Config Migration Controller API
Events.com Agent Email Controller API
Events.com Agent Job Update Controller API
Events.com Agent MCP API
Events.com Agent MCP Config Controller API
Events.com Agent Memory API
Events.com Agent Skill Controller API
Events.com Agent Template Controller API
Events.com AI Feedback Controller API
Events.com AI Third Party Page Controller API
Where this information came from

This is an independent, third-party profile of Events.com Alert History API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.