openapi: 3.1.0
info:
title: Signal AI Affinity Events API
description: "# Overview\n\nThe Signal AI API is an HTTP+JSON API offering programmatic access to Signal AI's decision augmentation platform.\nSignal AI has the world's largest dataset of real-time, global news and regulatory information. Our proprietary AIQ framework understands, enriches and surfaces relevant news and regulatory data in real-time, and at scale.\n\nOur API offers three powerful capabilities:\n\n1. **Content Search**: Create hyper-relevant content feeds using Signal's AI-powered search\n1. **Content Metrics**: Get coverage & sentiment metrics at a glance to power Business Intelligence & data visualisation solutions\n1. **Affinity**: Uncover unknowns through the Signal AI Knowledge Graph\n1. **Events**: Identify significant clusters of news coverage about entities and topics of interest\n\nTo be able to interact with the Signal AI API endpoints and get the most value out of them, it is useful to understand the metadata concepts that our AI enriches content with.\n\n# Concepts\n\n## Topics\n\nSignal AI experts have trained over 300 topics (or themes), from Health to Blockchain to provide clients an easy way to track emerging trends relevant to their businesses.\nClients can also train their own topics with help from our experts for use in our API.\nThe API provides the ability to query for documents pertaining to one or many topics. Examples of topics include: `Renewable Energy`, `Autonomous Vehicles`, `Corporate Responsibility`, `Artificial Intelligence`, etc.\n\n## Entities\n\nOur world-leading entity extraction ensures you never miss updates about the people, places or companies you or your clients care about most. Signal AI uses machine learning to identify and disambiguate these entities so it can discern between _‘Iceland’_ the supermarket and _‘Iceland’_ the country.\nThe API provides the ability to query for mentions of one or many entities. Examples of entities include: `Tim Cook`, `Apple Inc.`, `United States`, `Hong Kong`, etc.\n\n### Sentiment\n\nOur proprietary AIQ framework looks at the context within articles to identify the sentiment around every mention of an entity in the article's content.\nFor example, if an article mentions _“Volvo’s new electric vehicles provide better range than the Tesla Model 3”_, Signal AI will recognise Volvo as having a positive sentiment while Tesla as negative.\nEach mention is then given a `negative`, `neutral`, or `positive` label which is included in the metadata returned with each document. In addition, an aggregated document-level sentiment label is also computed for each entity, indicating the overall sentiment around this entity in the document.\nSentiment labels are only attached to entities and their mentions, and not to topics.\n\n### Salience\n\nA salience score is computed for every entity found in an article. It provides information about the importance or centrality of that entity to the entire article text. The higher the score, the more the article is ‘about’ the entity. We expose this as a `salient` boolean attribute if the score is above a threshold.\nThe `salience-rank` of the entity is the rank order of each entity's salience score. The entity of rank 1 is the most central to the article. It is possible that an article contains no salient entities.\n\nWhen querying by entity, it is also possible to increase the relevance of results by restricting the search to documents for which these entities are salient, using the `where.entities.salient-only` flag.\n\nNext, we describe the different API endpoints that enable these capabilities\n\n# Authorization\n\nAccess to the API is authorized using OAuth2 Bearer Tokens.\n\n<!-- ReDoc-Inject: <security-definitions> -->\n\n# Endpoints\n\n## Concept Discovery\n\nThe following endpoints allow the exploration of Signal AI's trained concepts (topics and entities), and publication sources, for the purpose of crafting content search and affinity-related queries.\n\n### `/topics`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n https://api.signal-ai.com/topics?name=environment&size=10\n```\n\n### `/categories/iptc-media-topics`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n https://api.signal-ai.com/categories/iptc-media-topics\n```\n\n### `/entities`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n https://api.signal-ai.com/entities?type=person&name=cook&size=10\n```\n\n### `/sources`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n https://api.signal-ai.com/sources?name=times&size=10\n```\n\n### `/source-locations`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n https://api.signal-ai.com/source-locations\n```\n\n## Content Search\n\nThis endpoint allows searching through Signal AI's vast content datasets, using a sophisticated query language.\n\n### `/search`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n -X POST \\\n -d '{ \"where\": { \"entities\": { \"id\": { \"eq\": \"11cab8df-4be1-470f-8f49-8f7f0863ec95\" } } } }' \\\n https://api.signal-ai.com/search\n```\n\n## Content Metrics\n\nThis endpoint provides aggregated metrics over all our news & regulatory content.\n\n### `/metrics`\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n -X POST \\\n -d '{ \"where\": { \"entities\": { \"id\": { \"eq\": \"11cab8df-4be1-470f-8f49-8f7f0863ec95\" } } },\n \"aggregations\": { \"group-by\": [\"published-at\", \"country\"], \"metrics\": [\"document-count\"] } }' \\\n https://api.signal-ai.com/metrics\n```\n\n## Affinity\n\nThe Affinity API allows users to discover connections between entities (e.g.\ncompanies) and topics, understand their proximity, and how it develops over\ntime, providing them with actionable intelligence about reputational risks and\ncommunication opportunities. It is powered by the Signal AI Knowledge Graph,\nwhich is generated by analyzing millions of documents every day.\n\n```bash\ncurl \\\n -H \"Authorization: Bearer eyJhbGciOi…\" \\\n -H \"Content-Type: application/json\" \\\n -X POST \\\n -d '{ \"relationship\": { \"type\": \"proximity\", \"date\": { \"start\": \"2022-01\", \"end\": \"2022-01\" }, \"interval\": \"month\", \"limit-per-interval\": 10 },\n \"source-concept\": {\"id\": \"11cab8df-4be1-470f-8f49-8f7f0863ec95\"},\n \"target-concepts\": { \"types\": [\"topic\"] } }' \\\n https://api.signal-ai.com/affinity\n```\n\n## Events\n\nThe Events API enables monitoring of major news events, allowing users to easily identify changes that could impact them or their business. By leveraging the 15-month archive, users can easily get up to speed on the recent developments involving specific companies, industries or topics.\n\n```bash\ncurl \\\n-H 'Authorization: Bearer eyJhbGc...' \\\n-H 'Content-Type: application/json' \\\n-X POST \\\n-d '{\n \"where\": {\n \"date\": {\n \"gte\": \"2022-05-01\",\n \"lte\": \"2022-05-30\"\n },\n \"entities\": {\n \"id\": {\"any\": [\"aee5dfa5-cf7e-4bcd-80c3-79b0125effc8\"]}\n }\n },\n \"size\": 50\n}' \\\nhttps://api.signal-ai.com/events\n```\n\n# Pagination\n\nSome of our endpoints such as `/search` and `/entities` limit the number of results returned in the response. Often there is a `size` parameter that controls how many results should be returned per page. To get additional results you will need to use pagination.\n\nEndpoints that have pagination will include a `next-cursor` field in the response. This can be used to fetch additional results by issuing further requests with the same query and specifying a `from-cursor` parameter. The value of `next-cursor` from the last response should be used to set the `from-cursor` parameter. For `GET` requests this will need to be specified in the query parameter. For `POST` requests this will need to be specified in the request body.\n\nThe absence of `next-cursor` in the response indicates that you have consumed all results matching the query.\n\n# Rate Limiting\n\nWe put limits on all API requests to protect our system from receiving more requests than it can handle, and to ensure an equitable distribution of the system resources across API clients.\nThe following API rate limits apply on a per-endpoint, per-Client ID basis:\n\n| Endpoint | requests/second | requests/minute |\n| ---------------- | --------------- | --------------- |\n| Content search | 2 | 30 |\n| Content metrics | 2 | 15 |\n| Concept affinity | 2 | 30 |\n| All others | 5 | 60 |\n\n# Error responses\n\n### 400 – Bad request\n\nThe request is invalid. This could be due to invalid parameters or invalid\nvalues. The error response will contain a top level field called `errors`\nlisting the errors. Each error is reported as a tuple:\n\n- the first element indicates which element is invalid, potentially providing a\n path to the incorrect field in the form `#/{type}/path/to/error` with `{type}`\n one of:\n - `query-params` for errors in URL parameters (or query string parameters)\n - `path-params` for errors in the URL (usually invalid resource ID)\n - `body` for errors in the body (for `POST` requests)\n- the second element contains an indication about the error\n\nExample of an error message:\n\n```json\n{\n \"errors\": [\n [\"#/query-params/sizee\", \"Invalid parameter\"],\n [\"#/path-params/id\", \"String does not match format \\\"uuid\\\"\"],\n [\n \"#/body/relationship/date/start\",\n \"must not be older than 15 months ago (2000-01)\"\n ]\n ]\n}\n```\n\n### 401 – Unauthorized\n\nIncorrect credentials, refer to the [Authorization](#section/Authorization)\nsection for more information.\n\n### 404 – Not found\n\nInvalid endpoint or unknown resource. For \"GET\" requests in particular (e.g.\n`GET /entities/{id}`) the body of the response will hold the invalid field.\n\n### 429 – Too many requests\n\nThe server received too many requests in the last second or minute. The [rate\nlimiting](#section/Rate-Limiting) section lists the limits for each endpoints.\n\n### 500 – Internal server error\n\nThe server encountered a problem while processing the request and failed\nunexpectedly. These errors are actively monitored and are automatically reported\nto our team so they can be investigated and fixed.\n\n### 502/503/504 – Gateway error / service unavailable\n\nThese error responses mean that the server either returned an invalid response\nor could not respond in time. For example, this could be due to unexpected high\nload on the server. It is usually safe to retry the request after some time.\n\n# Dates & Time Zones\n\nThe time zone that dictates the publication date is UTC. To be more precise, dates should respect the ISO 8601 format, where “Z” indicates UTC+0.\n\n# Changelog\n\n## v1.4 - 04/04/2023\n\n- Events GA\n - Added support for pagination\n - Added `/events/{hash}` endpoint\n\n## v1.3 - 28/07/2022\n\n- New Events capability\n - Added the new `events` endpoint for monitoring major news events\n - Enabled story-level metrics in the `metrics` endpoint to support volume and sentiment analysis of events\n\n## v1.2 - 08/06/2022\n\n- Improved Search capability\n - Added support for `story-id` as a search query criterion\n - Added support for `source.region` and `source.subregion` as search query criteria\n\n## v1.1 - 17/02/2022\n\n- Improved Affinity capability\n\n - Added the new `affinity` endpoint for querying relationships between concepts\n - Deprecated the existing `affinity/entities` and `affinity/topics` endpoints\n - Improved the `proximity-score` and `sentiment-score` models for better explainability and precision\n\n New endpoint:\n\n - `POST /affinity`\n\n Deprecated endpoints:\n\n - `GET /affinity/entities`\n - `GET /affinity/topics`\n"
version: v1.3
servers:
- url: https://api.signal-ai.com
security:
- OAuth2:
- default
tags:
- name: Events
description: '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 hashes
Each 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 included
In 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.
'
paths:
/events/{hash}:
get:
operationId: get-event-by-hash
tags:
- Events
summary: Returns the Event for this hash
parameters:
- name: hash
required: true
in: path
schema:
$ref: '#/components/schemas/EventHash'
responses:
'200':
description: Event's data
content:
application/json:
schema:
$ref: '#/components/schemas/EventHashResponse'
examples:
event-hash-response:
$ref: '#/components/examples/event-hash-response-example'
/events:
post:
operationId: search-events
security:
- OAuth2:
- events
tags:
- Events
summary: Events Search
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/EventSearchQuery'
examples:
events-request:
$ref: '#/components/examples/events-request-example'
responses:
'200':
description: Returns a list of events matching the query
content:
application/json:
schema:
$ref: '#/components/schemas/EventSearchResponse'
examples:
events-response:
$ref: '#/components/examples/events-response-example'
components:
schemas:
EventSearchResponse:
type: object
required:
- events
- event-hash-expiry
- stats
additionalProperties: false
properties:
events:
type: array
items:
unevaluatedProperties: false
$ref: '#/components/schemas/Event'
event-hash-expiry:
type: string
format: date-time
description: When the event hashes will expire (note that it could still be available after this time).
next-cursor:
oneOf:
- $ref: '#/components/schemas/Base64String'
- type: 'null'
description: Use the value of this field as the input to `from-cursor` in a query to paginate through the results (see [Pagination](#section/Pagination)).
stats:
type: object
description: The number of events matched across our entire data set. We can only provide an accurate figure up to 10000. Anything above that is indicated with `gte`.
required:
- total
properties:
total:
type: array
prefixItems:
- enum:
- eq
- gte
- type: integer
PartialTopic:
type: object
required:
- id
- name
properties:
id:
$ref: '#/components/schemas/ResourceId'
name:
type: string
EventHash:
type: string
pattern: '[0-9a-fA-F=-]+'
ResourceIds:
type: array
items:
$ref: '#/components/schemas/ResourceId'
Event:
type: object
required:
- hash
- date
- story-count-global
- document-count-entitlements
- document-count-global
- labels
- entities
- topics
- story-ids
properties:
labels:
type: array
items:
type: string
description: The most descriptive words or phrases that appear in the documents in the event.
date:
$ref: '#/components/schemas/Date'
document-count-entitlements:
type: integer
description: The number of documents that mentioned this event based on your user permissions.
hash:
$ref: '#/components/schemas/EventHash'
story-count-global:
type: integer
description: The number of stories that mentioned this event across Signal's global data set.
story-ids:
type: array
description: Ordered by centrality - how well the story represents the event in question. You can use these ids in the [Search API](#tag/Content-Search/operation/search-documents) to get headlines best describing the event.
items:
$ref: '#/components/schemas/ResourceId'
document-count-global:
type: integer
description: The number of documents that mentioned this event across Signal's global data set.
entities:
type: array
items:
$ref: '#/components/schemas/EventEntity'
topics:
type: array
items:
$ref: '#/components/schemas/EventTopic'
source-count-global:
oneOf:
- type: integer
- type: 'null'
description: The number of sources that mentioned this event across Signal's global data set.
EventSearchQuery:
type: object
required:
- where
additionalProperties: false
properties:
where:
$ref: '#/components/schemas/EventMatch'
exclude:
$ref: '#/components/schemas/EventExclude'
size:
type: integer
default: 10
minimum: 0
maximum: 1000
from-cursor:
$ref: '#/components/schemas/Base64String'
description: Use this field to paginate through the results (see [Pagination](#section/Pagination)).
Entity:
type: object
required:
- id
- name
- type
properties:
id:
$ref: '#/components/schemas/ResourceId'
type:
$ref: '#/components/schemas/EntityType'
name:
type: string
EventEntitiesMatch:
type: object
additionalProperties: false
required:
- id
properties:
id:
allOf:
- $ref: '#/components/schemas/AnyOrAllResourceIdsMatch'
- properties:
any:
type: array
maxItems: 200
all:
type: array
maxItems: 200
ResourceId:
type: string
format: uuid
pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
example: bcd2d868-ed38-4382-b94a-622a30fc3215
EventTopic:
type: object
allOf:
- $ref: '#/components/schemas/PartialTopic'
- properties:
story-count:
type: integer
prominence-score:
type: number
description: The number of stories mentioning the concept divided by the story count for the event. For example, if half the stories in the event mention a topic then the prominence would be 0.5.
AnyResourceIds:
type: object
additionalProperties: false
required:
- any
properties:
any:
$ref: '#/components/schemas/ResourceIds'
Date:
type: string
format: date
description: "A date based on the IETF RFC 3339 format (e.g. `2023-01-01`).\n Note that a day is the span of time between 00:00:00 and 23:59:59 based on\n the UTC timezone. You may prefer using the `date-time` option to match days\n in a different timezone."
example: '2023-01-01'
Base64String:
type: string
pattern: ^([A-Za-z0-9+/]{4})*([A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{2}==)?$
example: RjQ2RTRBQUEtQTNGRi00MEI3LUE1NEYtNTA0NEQxMjc5NkU3
AnyOrAllResourceIdsMatch:
oneOf:
- $ref: '#/components/schemas/AnyResourceIds'
- $ref: '#/components/schemas/AllResourceIds'
EventMatch:
type: object
additionalProperties: false
properties:
date:
type: object
properties:
gt:
$ref: '#/components/schemas/Date'
gte:
$ref: '#/components/schemas/Date'
lt:
$ref: '#/components/schemas/Date'
lte:
$ref: '#/components/schemas/Date'
additionalProperties: false
minProperties: 1
dependentSchemas:
gt:
not:
required:
- gte
gte:
not:
required:
- gt
lt:
not:
required:
- lte
lte:
not:
required:
- lt
topics:
$ref: '#/components/schemas/EventTopicsMatch'
entities:
$ref: '#/components/schemas/EventEntitiesMatch'
labels:
type: object
description: Filter on specific words or phrases. A label can contain a maximum of 6 words.
oneOf:
- additionalProperties: false
properties:
any:
type: array
items:
type: string
maxItems: 100
- additionalProperties: false
properties:
all:
type: array
items:
type: string
maxItems: 100
sources:
type: object
additionalProperties: false
required:
- id
description: If the user does not have access to any of the sources specified, those ids will be excluded while fetching the events
properties:
id:
allOf:
- $ref: '#/components/schemas/AnyOrAllResourceIdsMatch'
- properties:
any:
maxItems: 100
all:
maxItems: 100
EntityType:
type: string
enum:
- person
- organisation
- location
- substance
- disease
- product
- regulation
AllResourceIds:
type: object
additionalProperties: false
required:
- all
properties:
all:
$ref: '#/components/schemas/ResourceIds'
EventEntity:
type: object
allOf:
- $ref: '#/components/schemas/Entity'
- properties:
story-count:
type: integer
prominence-score:
type: number
description: The number of stories mentioning the concept divided by the story count for the event. For example, if half the stories in the event mention an entity then the prominence would be 0.5.
EventHashResponse:
type: object
required:
- event
additionalProperties: false
properties:
event:
type: object
unevaluatedProperties: false
allOf:
- $ref: '#/components/schemas/Event'
- required:
- source-ids
properties:
source-ids:
type: array
items:
$ref: '#/components/schemas/ResourceId'
description: The sources that mention this event.
EventExclude:
type: object
additionalProperties: false
properties:
entities:
type: object
additionalProperties: false
required:
- id
properties:
id:
allOf:
- $ref: '#/components/schemas/AnyResourceIds'
- properties:
any:
maxItems: 100
topics:
type: object
additionalProperties: false
required:
- id
properties:
id:
allOf:
- $ref: '#/components/schemas/AnyResourceIds'
- properties:
any:
maxItems: 50
labels:
type: object
additionalProperties: false
properties:
any:
type: array
items:
type: string
maxItems: 100
sources:
type: object
additionalProperties: false
required:
- id
properties:
id:
allOf:
- $ref: '#/components/schemas/AnyResourceIds'
- properties:
any:
maxItems: 100
EventTopicsMatch:
type: object
additionalProperties: false
required:
- id
properties:
id:
allOf:
- $ref: '#/components/schemas/AnyOrAllResourceIdsMatch'
- properties:
any:
maxItems: 100
all:
maxItems: 100
examples:
events-response-example:
value:
events:
- labels:
- apple
- apple pay
- eu
- mobile
- european commission
- payment
- dominant
date: '2022-05-02'
document-count-entitlements: 3773
hash: 01e6-5f0a8e41-834dc94d-995011f6-0717dc49
story-count-global: 1298
story-ids:
- 304c5ded-f186-43cc-868e-c6b537b3b5e4
- 0ee8d6c5-33e0-442d-b257-14115be69e0a
- 39ae8606-4434-4427-888f-7904930a007d
document-count-global: 4306
entities:
- name: Apple Inc.
id: aee5dfa5-cf7e-4bcd-80c3-79b0125effc8
type: organisation
story-count: 1296
prominence-score: 0.9984591679506933
- name: European Union
id: 1eedf0d9-f4c3-4b8f-90c4-31e6862dfa56
type: organisation
story-count: 847
prominence-score: 0.652542372881356
source-ids:
- 000a992d-6bbc-410c-bccd-d20a9aafff58
- 002c55f5-ed67-4273-a6b8-cefb911bc095
topics:
- name: Engineering
id: bb422b16-7eef-40b1-9cd8-82085de351bb
story-count: 1241
prominence-score: 0.9560862865947611
- name: Market Regulation
id: eb920503-7b82-4e56-8713-b091b7a1d442
story-count: 1234
prominence-score: 0.9506933744221879
source-count-global: 2832
- labels:
- password
- apple google and microsoft
- fido
- passwords
- passwordless
- microsoft
- login
- google
- apple
date: '2022-05-06'
document-count-entitlements: 915
hash: 01ea-864a924c-876ddbc5-fdfc6d72-a317284f
story-count-global: 603
story-ids:
- 79ef9f05-3e0f-4eeb-87e5-2f3a87cfb618
- a34fc505-4904-4089-81ac-0eda798d5cc7
- c5f2e79e-6454-4bbf-b969-5933a121e711
document-count-global: 979
entities:
- name: Google
id: 6d1cde63-7ff9-410a-a63c-a6741802858b
type: organisation
story-count: 577
prominence-score: 0.956882255389718
- name: Apple Inc.
id: aee5dfa5-cf7e-4bcd-80c3-79b0125effc8
type: organisation
story-count: 572
prominence-score: 0.9485903814262023
topics:
- name: Engineering
id: bb422b16-7eef-40b1-9cd8-82085de351bb
story-count: 600
prominence-score: 0.9950248756218906
- name: Digital Futures
id: c61a8b5c-80fc-4f20-99ed-1a40670660ca
story-count: 517
prominence-score: 0.857379767827529
source-count-global: 650
event-hash-expiry: '2023-04-04T15:18:04.346649853Z'
next-cursor: WzE4NCwiMDFmZS1jZTVhNWUwMS1iMmM0NmQ2Zi1iNjQ1MzczNi0yNjcyNTA0YSJd
stats:
total:
- eq
- 7614
events-request-example:
summary: All events related to Apple during May 2022
value:
where:
date:
gte: '2022-05-01'
lte: '2022-05-30'
entities:
id:
any:
- aee5dfa5-cf7e-4bcd-80c3-79b0125effc8
size: 10
event-hash-response-example:
value:
event:
labels:
- apple
- apple pay
- eu
- mobile
- european commission
- payment
- dominant
date: '2022-05-02'
document-count-entitlements: 3773
hash: 01e6-5f0a8e41-834dc94d-995011f6-0717dc49
story-count-global: 1298
story-ids:
- 304c5ded-f186-43cc-868e-c6b537b3b5e4
- 0ee8d6c5-33e0-442d-b257-14115be69e0a
- 39ae8606-4434-4427-888f-7904930a007d
document-count-global: 4306
entities:
- name: Apple Inc.
id: aee5dfa5-cf7e-4bcd-80c3-79b0125effc8
type: organisation
story-count: 1296
prominence-score: 0.9984591679506933
- name: European Union
id: 1eedf0d9-f4c3-4b8f-90c4-31e6862dfa56
type: organisation
story-count: 847
prominence-score: 0.652542372881356
source-ids:
- 000a992d-6bbc-410c-bccd-d20a9aafff58
- 002c55f5-ed67-4273-a6b8-cefb911bc095
topics:
- name: Engineering
id: bb422b16-7eef-40b1-9cd8-82085de351bb
story-count: 1241
prominence-score: 0.9560862865947611
- name: Market Regulation
id: eb920503-7b82-4e56-8713-b091b7a1d442
story-count: 1234
prominence-score: 0.9506933744221879
source-count-global: 2832
securitySchemes:
OAuth2:
type: oauth2
description: "To obtain the Bearer Token using the Client ID / Secret pair provided to you:\n\n```bash\ncurl -X POST \\\n -d 'grant_type=client_credentials' \\\n -d 'client_id=YOUR_CLIENT_ID' \\\n -d 'client_secret=YOUR_CLIENT_SECRET' \\\n https://api.signal-ai.com/auth/token\n```\n\nThis will return the following JSON response:\n\n```json\n{\n \"access_token\": \"eyJhbGciOi…\",\n \"expires_in\": 86400,\n …\n}\n```\n\nYou must send the `access_token` from this response in the Authorization header when making requests to other API endpoints:\n\n```bash\ncurl -H \"Authorization: Bearer eyJhbGciOi…\" \\\n https://api.signal-ai.com/…\n```\n\nAccess tokens will expire 24 hours from the time they were issued.\n"
flows:
clientCredentials:
tokenUrl: https://api.signal-ai.com/auth/token
scopes:
default: Access to discovery endpoints
search: Access to content search endpoint
metrics: Access to content metrics endpoint
affinity: Access to concept affinity endpoints
events: Access to events endpoint
risk-events: Access to risk events
x-tag
# --- truncated at 32 KB (32 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/signal-ai/refs/heads/main/openapi/signal-ai-events-api-openapi.yml