Documentation Index
Fetch the complete documentation index at: https://docs.akta.pro/llms.txt
Use this file to discover all available pages before exploring further.
Quick start
The Company News Monitoring API returns the latest news articles for a given company. Each result is enriched with an AI-generated summary, event classification, publisher metadata, sentiment, company mentions, geography, industry tags, and scraped article text. Results are returned synchronously in the HTTP response.This is a synchronous API. The results are returned directly in the HTTP response. Use
limit and offset to paginate larger result sets.Endpoint
Method: GET/api/v1/company/news/
Base URL
https://api.akta.pro
Authentication
Pass your API key in thex-api-key request header.
-H "x-api-key: YOUR_API_KEY"
Sample request
Request reference
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
company | string | Yes | Company permalink or valid company URL for which news articles should be fetched. Example: tesla. |
start_date | string | No | Start date for the news timeframe, formatted as YYYY-MM-DD. |
end_date | string | No | End date for the news timeframe, formatted as YYYY-MM-DD. |
category | string | No | Comma-separated list of news categories to include. Category names must be URL-encoded when sent in a raw query string. |
limit | integer | No | Maximum number of news articles to return in the current response. |
offset | integer | No | Number of records to skip before returning results. Use this with limit for pagination. |
blacklisted | string | No | Comma-separated list of publisher domains to exclude from results. Include the publisher domain only, for example wokelo.ai. |
Filtering by selected categories
Usecategory when you only want specific types of company events. Multiple categories should be passed as a comma-separated string.
Response
A successful response returns a status, article array, count of records in the current response, total matching articles, and pagination metadata.Top-level response fields
| Field | Type | Description |
|---|---|---|
status | string | Request status. Successful requests return success. |
data | array | Array of company news article objects. |
count | integer | Number of article objects returned in the current response. |
total | integer | Total number of articles matching the request filters. |
limit | integer | Maximum number of articles requested for the current response. |
offset | integer | Number of records skipped before the current response. |
Article object fields
| Field | Type | Description |
|---|---|---|
ai_summary | string | AI-generated summary of the article. |
type | string | Event type assigned to the article. |
url | string | Source article URL. |
title | string | Article headline. |
company_name | string | Primary company associated with the article. |
publisher | string | Publisher or source domain label. |
published_date | string | Publication timestamp returned by the API. |
author | string | Article author, when available. |
countries | array of strings | Countries associated with the article. |
sentiment | string | Sentiment classification for the article. Example: Positive, Neutral. |
company_names | array of objects | Companies mentioned in the article, with name and website where available. |
primary_tag | string | Primary news category or event tag assigned to the article. |
original_language | string | Original language code for the article. Example: EN. |
secondary_tags | array of strings | Additional categories or event tags assigned to the article. |
newsworthiness_impact | string | Estimated impact level of the article. Example: Medium. |
primary_industry | string | Primary industry classification associated with the article. |
secondary_industry | array of strings | Additional industry classifications associated with the article. |
scraped_text | string | Extracted article text. |
Pagination
Uselimit and offset together to paginate through matching articles.
The response includes both
count and total. Use count to understand how many records were returned in the current response, and total to understand how many records match the filters overall.Common monitoring use cases
Portfolio adverse signal monitoring
Fetch legal, compliance, layoff, leadership change, governance, and workforce-related news for a portfolio company.Capital markets and transaction monitoring
Track financing, transaction, strategic development, and governance events for a target company.Implementation notes
- Use
companyfor the target company identifier and add a date range when monitoring a defined period. - Use
categoryto narrow results to event types that matter for the workflow. - Use
blacklistedto exclude irrelevant or low-value publishers. - Use
limitandoffsetfor pagination rather than requesting a large result set at once. - Store
url,title,published_date,publisher,primary_tag,sentiment, andai_summaryfor most monitoring dashboards. - Store
scraped_textonly when downstream workflows need full article text.