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

Signal AI Events API

The Events API endpoint identifies significant clusters of news coverage about entities and topics of interest, allowing users to easily identify news events that could impact them or their business, and offering a qualitative deep dive into the quantitative data provided by Metrics and Affinity. By leveraging the 15-month archive, users can easily get up to speed on the recent developments involving specific companies, industries or topics.Examples of questions this data can answer include:* Have there been any events involving Company X in the past day/month/year/15 months?* What are the latest developments in the food and beverage industry?* Have there been any product recalls recently?The data returned includes entities and topics involved, their prominence scores, alongside the number of stories describing the event (a measure of "newsworthiness"), and a group of the most descriptive labels.The data is generated daily.## Event hashesEach event contains a `hash` field. You can look up events by hash using the `/events/{hash}` endpoint. The difference between the data returned in this endpoint compared with `/events` is as follows:* All story ids for the event are returned not just the top 100* The source ids for the event are includedIn APIs it's more common to use the term "id" rather than "hash". We've chosen to use "hash" because these strings can change as we receive new data. In the `/events` endpoint the `event-hash-expiry` field indicates when the hash will expire. Note that it could still be available after this time.

Signal AI Events API is one of 11 APIs that Signal AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version v1.3.

Requests are made against a single base URL, https://api.signal-ai.com.

2 operations 2 paths 21 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.3
Base URL
https://api.signal-ai.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Signal AI Events API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 6 scopes. By default, every request must be authenticated.

  • OAuth2 — To obtain the Bearer Token using the Client ID / Secret pair provided to you: bash curl -X POST \ -d 'granttype=clientcredentials' \ -d 'clientid=YOURCLIENTID'…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Events 2

The Events API endpoint identifies significant clusters of news coverage about entities and topics of interest, allowing users to easily identify news events that could impact the…

GET
/events/{hash}
Returns the Event for this hash
get-event-by-hash 1 param → 200
POST
/events
Events Search
search-events body → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are Event (10 properties), EventMatch (5 properties), EventSearchResponse (4 properties), EventSearchQuery (4 properties). Each schema is shown below with its type and property counts.

AnyResourceIds
object
1 property 1 required
AllResourceIds
object
1 property 1 required
Date
string
A date based on the IETF RFC 3339 format (e.g. 2023-01-01). Note that a day is the span of time between 00:00:00 and 23:59:59 based on the UTC timezone. You ma…
ResourceIds
array
EventTopic
object
EventTopicsMatch
object
1 property 1 required
EntityType
string
ResourceId
string
Event
object
10 properties 9 required
Base64String
string
EventSearchResponse
object
4 properties 3 required
EventMatch
object
5 properties
EventHashResponse
object
1 property 1 required
EventHash
string
EventEntity
object
EventEntitiesMatch
object
1 property 1 required
Entity
object
3 properties 3 required
EventExclude
object
4 properties
EventSearchQuery
object
4 properties 1 required
AnyOrAllResourceIdsMatch
PartialTopic
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signal-ai-events-api-openapi.yml Raw ↑

Other APIs Signal AI publishes across the network.

Signal AI Affinity API
Signal AI Categories API
Signal AI Content Metrics API
Signal AI Content Search API
Signal AI Entities API
Signal AI Openapi.json API
Signal AI Publication sources API
Signal AI Risk Events API
Signal AI Topics API
Signal AI Organisation API
Where this information came from

This is an independent, third-party profile of Signal AI Events 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.