Aevum News API

Access Aevum News' comprehensive journalistic database, real-time breaking alerts, and author metrics programmatically. Designed for developers, researchers, and media platforms.

Note: All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API changes are documented in the changelog.

Base URL

All endpoints are relative to:

https://api.aevum.news/v1

Authentication

Aevum News uses API keys to authenticate requests. You can view and manage your API keys in the developer dashboard.

Include the API key in the request headers:

HTTP
Authorization: Bearer your_api_key_here
Content-Type: application/json

Security Note: Keep your API keys secure. Do not share them publicly or commit them to version control.

Endpoints

Articles

GET /articles Returns a paginated list of articles. Supports filtering by category, date, and language.
limit
Max articles to return
OPT
offset
Cursor for pagination
OPT
category
e.g., tech, politics, world
OPT
language
ISO 639-1 code
REQ
cURL
Node.js
Python
curl https://api.aevum.news/v1/articles?category=tech&language=en \\
  -H "Authorization: Bearer YOUR_KEY"
GET /articles/:id Retrieves a single article by its unique identifier.
GET /search Full-text search across titles, summaries, and body content.
q
Search query
REQ
sort
relevance, date
OPT
date_from / date_to
ISO 8601
OPT

Authors

GET /authors/:slug Returns author profile, bio, publication count, and recent articles.

Webhooks

POST /webhooks Register event listeners for breaking news, article publication, and author updates.
url
HTTPS endpoint
REQ
events
Array: ["article.published", "breaking_alert"]
REQ
secret
Webhook signature key
OPT

Rate Limits

API requests are throttled based on your tier. Exceeding limits returns 429 Too Many Requests.

TierRequests / MinuteRequests / Day
Free605,000
Pro600100,000
EnterpriseCustomCustom

Rate limit headers are included in every response:

X-RateLimit-Limit: 600 | X-RateLimit-Remaining: 598 | X-RateLimit-Reset: 1698765432

Error Codes

CodeDescriptionCommon Causes
400Bad RequestInvalid JSON, missing required params
401UnauthorizedInvalid or expired API key
403ForbiddenInsufficient permissions for resource
404Not FoundEndpoint or resource doesn't exist
429Too Many RequestsRate limit exceeded
500Internal Server ErrorAevum News backend failure (retry with backoff)

Standard Error Response Format:

{
  "error": {
    "code": 401,
    "message": "Invalid API key provided.",
    "request_id": "req_9x8y7z6w5v"
  }
}

Changelog