Aevum News Documentation

Comprehensive guide for developers, publishers, and contributors integrating with the Aevum News API and publishing platform. Access real-time news data, submit verified content, and maintain editorial standards.

REST API OAuth 2.0 GraphQL Available Webhooks

Overview

The Aevum News platform provides a unified interface for accessing verified global news, managing editorial content, and integrating journalism workflows into external applications. Our API supports JSON and XML responses, real-time streaming via WebSocket, and bulk data exports for enterprise partners.

💡 Base URL All API requests should be made to: https://api.aevumnews.com/v2

Quick Example

const response = await fetch('https://api.aevumnews.com/v2/articles?category=world&limit=5', {
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Accept': 'application/json'
  }
});
const articles = await response.json();

Authentication

Aevum News uses standard OAuth 2.0 and API key authentication. All endpoints requiring authentication will return a 401 Unauthorized response if credentials are missing or invalid.

Header	Required	Description
`Authorization`	Yes	Bearer token format: `Bearer <token>`
`X-Aevum-Key`	Optional	Legacy API key for backward compatibility
`Content-Type`	Yes	`application/json` or `application/xml`

⚠️ Security Note Never expose API keys in client-side code. Use environment variables or a secure proxy server for production applications. Rotate keys every 90 days via the developer dashboard.

API Reference

Articles

GET /articles

Retrieve paginated list of published articles with filtering and sorting capabilities.

Parameter	Type	Required	Description
`category`	string	No	Filter by category (world, tech, business, etc.)
`status`	string	No	Filter by status: published, draft, pending_review
`limit`	integer	No	Results per page (1-100, default: 20)
`sort`	string	No	Sort order: created_desc, updated_asc, relevance

POST /articles

Submit a new article for editorial review. Requires writer or editor role.

{
  "title": "Global Climate Accord Reaches Milestone",
  "slug": "global-climate-accord-milestone",
  "body": "<p>Detailed verified report content...</p>",
  "category": "world",
  "tags": ["climate", "policy", "summit"],
  "source_verification": "cross_referenced_3",
  "author_id": "usr_8a92f1",
  "status": "pending_review"
}

Categories & Taxonomy

GET /categories

Returns hierarchical taxonomy tree with article counts and metadata.

Search & Filtering

GET /search

Full-text search with semantic ranking, date ranges, and source credibility scoring.

Parameter	Description
`q`	Search query string
`date_from`	ISO 8601 timestamp
`credibility_min`	Minimum source score (0.0-1.0)
`language`	ISO 639-1 code (e.g., en, es, fr)

Publishing Standards

Article Submission Workflow

All content submitted through the API or dashboard follows a strict editorial pipeline:

Draft Creation → Content stored with version control
Automated Checks → Plagiarism, grammar, and metadata validation
Fact-Verification Queue → Assigned to regional verification team
Editorial Review → Tone, structure, and compliance audit
Publication → Distributed across CDN and partner networks

✅ Best Practice Use the preview_url returned in the POST response to render WYSIWYG previews before final submission. Always include source_verification metadata for faster processing.

Required Metadata Schema

{
  "title": "string (required, max 120 chars)",
  "slug": "string (auto-generated if omitted)",
  "excerpt": "string (required, max 240 chars)",
  "body": "string (HTML sanitized on ingress)",
  "category": "string (enum: world, tech, business, science, culture, politics)",
  "tags": "array<string> (max 8)",
  "author_id": "string (UUID)",
  "sources": "array<{url, name, credibility_score}>",
  "publication_date": "string (ISO 8601)",
  "visibility": "string (public, restricted, embargo)"
}

Media & Asset Guidelines

Images: Max 5MB, preferred formats JPEG/WebP, minimum 1200px width
Videos: Hosted via Aevum Media CDN or provide S3-compatible URL
Infographics: Vector SVG preferred, fallback PNG required
All media requires alt text and attribution metadata

Editorial Guidelines

Fact-Checking Protocol

Aevum News maintains a zero-tolerance policy for unverified claims. Every article must pass:

Primary Source Verification → Minimum 2 independent credible sources
Temporal Validation → Dates, quotes, and statistics cross-referenced
Bias Assessment → Automated sentiment analysis + manual editorial review
Retraction Pathway → Clear amendment protocol if errors are discovered post-publication

Tone & Voice Standards

Content should maintain objectivity, clarity, and accessibility. Avoid speculative language, loaded adjectives, or unattributed opinions. Use active voice and precise terminology. When covering sensitive topics, follow our [Crisis Reporting Handbook](#).

Compliance & Ethics

All contributors must adhere to the International Federation of Journalists (IFJ) code of ethics. Data privacy (GDPR/CCPA), copyright compliance, and conflict-of-interest disclosures are mandatory. Automated systems flag potential violations before publication.

Support & Resources

Need help integrating or have editorial questions?

Developer Portal → Dashboard, API keys, usage analytics
SDKs → Official packages for JavaScript, Python, Go, and PHP
Community → Discord channel for real-time Q&A
Enterprise → Custom SLAs, dedicated support, private endpoints

📧 Contact Technical support: dev@support.aevumnews.com
Editorial inquiries: editorial@support.aevumnews.com