Welcome to Aevum News Documentation

Your comprehensive resource for understanding Aevum News' editorial standards, technical infrastructure, API capabilities, and organizational policies. Whether you're a journalist, developer, partner, or reader — this is your central hub.

Getting Started

Aevum News operates as a digital-first journalism platform with a distributed team of correspondents, editors, and analysts. This documentation covers every aspect of our operations, from editorial workflows to API access for partners.

🚀

Quick Start Guide

Get up and running in under 10 minutes. Perfect for new team members and developers.

🏗️

Architecture

Understand our tech stack, infrastructure, and how content flows through the platform.

🔌

API Reference

Full API documentation for integrating Aevum News content into your applications.

✏️

Editorial Standards

Our editorial guidelines, fact-checking protocols, and verification procedures.

What You'll Learn

Editorial Process: How stories are sourced, written, fact-checked, and published
Technical Infrastructure: Our CMS, CDN, and real-time delivery systems
API & Integration: Access our content via REST API or WebSocket feeds
Team & Governance: Our organizational structure and editorial independence policies
Analytics: How we measure impact and engagement across platforms

ℹ️

Who is this documentation for?

This documentation serves journalists, editors, developers, data partners, academic researchers, and anyone interested in how Aevum News operates. Navigate via the sidebar to find what you need.

About Aevum News

Aevum News is a globally distributed digital journalism platform founded in 2022. Our name derives from the Latin "aevum", meaning "age" or "eternity" — reflecting our commitment to journalism that endures beyond the 24-hour news cycle.

Our Mission

To deliver unfiltered, authoritative journalism that cuts through noise. We believe every story matters and every fact deserves rigorous verification. Our readers trust us not because we're the first to report, but because they know our reporting is always correct.

Key Principles

Principle	Description	Implementation
Independence	Editorial decisions are made solely by our editorial board	No corporate ownership; funded by readership
Transparency	All sources, corrections, and methodologies are public	Open correction policy, source attribution
Accuracy	Every fact is verified before publication	Multi-layer editorial review process
Balance	Multiple perspectives on every story	Diverse correspondent network across 120+ countries
Accountability	We stand behind every word we publish	Named authors, public corrections log

Our Reach

Correspondents in 120+ countries
25M+ monthly unique readers
50,000+ stories published annually
6 editorial offices across 4 continents
12 language editions

Editorial Guidelines

Our editorial guidelines form the backbone of every story we publish. They ensure consistency, accuracy, and fairness across all content produced by Aevum News.

Core Writing Standards

Inverted Pyramid: Most important information comes first
Active Voice: Prefer "The committee approved" over "Approval was given"
Attribution: Every claim must be attributed to a specific source
Neutral Tone: Avoid editorializing; let facts speak
Clarity: Write at an 8th-grade reading level minimum

⚠️

Common Pitfall: Unattributed Claims

Never write "research shows" or "experts agree" without naming the specific research or experts. Vague attribution undermines credibility.

Fact-Checking Protocol

1

Primary Source Verification

Every factual claim must be traceable to a primary source: official documents, direct statements, raw data, or firsthand accounts.

2

Corroboration

At least one independent secondary source must confirm the primary claim before publication.

3

Editorial Review

A senior editor reviews the story specifically for factual accuracy, cross-referencing all claims against sources.

4

Final Sign-off

The managing editor gives final approval. No story publishes without dual sign-off from field editor and managing editor.

API Access

Aevum News provides a comprehensive REST API that allows partners, developers, and data consumers to access our content programmatically. The API supports real-time story feeds, historical search, metadata, and analytics endpoints.

Quick Start

cURL

# Fetch latest stories 
curl -X GET \
  https://api.aevumnews.com/v2/stories \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

✅

Rate Limits

Free tier: 100 requests/hour. Partner tier: 10,000 requests/hour. Enterprise: Unlimited with dedicated infrastructure.

Authentication

All API requests require authentication via Bearer token. Obtain your API key from the Developer Portal. Keys are tied to your account and should never be exposed client-side.

Quick Start Guide

Get up and running with Aevum News in under 10 minutes. Whether you're a new team member, developer, or content partner, this guide walks you through the essentials.

For Developers

Step 1: Obtain API Credentials

1

Create an Account

Visit the Aevum Developer Portal and sign up with your organizational email. Verify your email within 24 hours to activate API access.

2

Generate API Key

Navigate to Settings → API Keys → Generate New Key. Choose your access level (Read-only, Read/Write, or Admin) and assign permissions.

3

Make Your First Request

JavaScript

const response = await fetch('https://api.aevumnews.com/v2/stories?limit=5', {
  headers: {
    'Authorization': `Bearer ${process.env.AEVUM_API_KEY}`,
    'Content-Type': 'application/json'
  }
});

const stories = await response.json();
console.log(`Found ${stories.total} stories`);

ℹ️

Environment Variables

Always store your API key in environment variables — never in source code. Aevum uses .env validation on deploy to prevent key leaks.

For Journalists & Editors

Step 1: Access the CMS

1

Get Your Credentials

Contact your editorial manager to receive access to the Aevum CMS at cms.aevumnews.com. You'll receive SSO credentials linked to your organizational identity.

2

Familiarize Yourself with the Dashboard

The dashboard shows your active stories, assigned beats, pending reviews, and editorial calendar. New users see an interactive tour on first login.

3

Start Your First Story

Click + New Story in the sidebar. Fill in the headline, lead paragraph, and body. The editor auto-saves every 30 seconds. Use the built-in fact-check checklist before submitting for review.

For Content Partners

📝

Content Licensing

Aevum News offers syndication agreements for verified content. Visit our Partnership Portal to explore licensing options, attribution requirements, and revenue sharing models.

Editorial Guidelines

The definitive reference for all Aevum News journalists, editors, and contributors. Every story published under the Aevum News banner must adhere to these standards.

Standards of Accuracy

Source Hierarchy

Aevum News classifies sources into four tiers of reliability. Stories must meet the minimum tier for their category:

Tier	Source Type	Acceptable For	Status
Tier 1	Primary documents, official records, direct witness accounts	All story types	Required for breaking
Tier 2	Expert analysis, peer-reviewed research, data sets	Analysis, features, data stories	Standard
Tier 3	Verified eyewitness accounts, social media (corroborated)	Breaking news (with corroboration)	Conditional
Tier 4	Anonymous sources	Investigative only (requires editor approval)	Restricted

🚫

Never use Tier 4 alone

Anonymous sources may never be the sole source of a claim. Every anonymous claim must be corroborated by at least one Tier 1 or Tier 2 source.

Corrections Policy

Aevum News maintains an open corrections policy. When errors are identified:

The error is verified by a different editor than the original author
The correction is published within 2 hours of verification
A correction notice appears at the top of the article and in the original publication
The correction log is maintained publicly on our Corrections Page
Significant corrections trigger an editorial board review of the process that allowed the error

Style Conventions

Numbers and Figures

Numbers 0–999: written as words (one, fifty, 999)
Numbers 1,000+: numerals (1,000, 15,000)
Currency: always use numerals with the currency symbol ($5 million, not five million dollars)
Percentages: numerals for 10%+ (12%), words for under 10% (eight percent)

Titles and Names

Use full title on first reference: President Xi Jinping
Use surname on subsequent references: Xi
Never use titles without names: write the president, not The President
Academic titles (Dr., Prof.) are used on first reference in expert commentary

Geographic References

First reference: full name + country (e.g., Paris, France)
Subsequent: city name only (Paris)
Use internationally recognized place names; note disputed territories with attribution

API Overview

The Aevum News API provides programmatic access to our content, metadata, and analytics. Built on REST principles with WebSocket support for real-time delivery.

Base URL

HTTP

https://api.aevumnews.com/v2

Response Format

All API responses are returned as JSON with consistent envelope structure:

JSON — Response Envelope

{
  "status": "success",
  "meta": {
    "request_id": "req_7f8d9a2b1c",
    "timestamp": "2025-01-15T14:30:00Z",
    "rate_limit": {
      "remaining": 9999,
      "reset_at": "2025-01-15T15:00:00Z"
    }
  },
  "data": { /* response payload */ }
}

Available Endpoints

GET /v2/stories Stable

Retrieve stories with optional filtering by category, region, date range, and author.

GET /v2/stories/{id} Stable

Get full content of a single story by ID, including metadata and source references.

GET /v2/categories Stable

List all available content categories and their article counts.

GET /v2/regions Stable

Retrieve geographic coverage data and active correspondents by region.

GET /v2/analytics/{story_id} Beta

Access engagement metrics for a specific story: views, shares, time-to-read, geographic breakdown.

POST /v2/feedback Stable

Submit content feedback or flag potential factual issues for editorial review.

GET /v2/corrections Stable

Retrieve the public corrections log, filterable by date, category, or severity.

Error Responses

The API uses standard HTTP status codes. Error responses follow the same envelope structure:

JSON — Error Response

{
  "status": "error",
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Too many requests. Retry after 2025-01-15T15:00:00Z.",
    "docs": "https://docs.aevumnews.com/api/errors#RATE_LIMIT_EXCEEDED"
  }
}

System Architecture

Aevum News runs on a distributed, cloud-native architecture designed for global scale, editorial independence, and zero-downtime publishing.

High-Level Architecture

Architecture Diagram

┌─────────────────────────────────────────────────────────────┐
│                    Reader / Client Layer                     │
│   ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌──────────────┐ │
│   │ Website │  │ Mobile  │  │ API     │  │ RSS/Feeds    │ │
│   └────┬────┘  └────┬────┘  └────┬────┘  └──────┬───────┘ │
└────────┼───────────┼─────────────┼──────────────┼──────────┘
         │           │             │              │
┌────────┼───────────┼─────────────┼──────────────┼──────────┐
│       ▼           ▼             ▼              ▼          │
│  ┌─────────────────────────────────────────────────────┐  │
│  │            CDN & Edge Cache (CloudFlare)            │  │
│  └──────────────────────────┬──────────────────────────┘  │
└──────────────────────────────┼──────────────────────────────┘
                               │
┌──────────────────────────────┼──────────────────────────────┐
│                              ▼                              │
│  ┌─────────────┐  ┌─────────────┐  ┌──────────────────┐   │
│  │   API GW    │  │  CMS/API    │  │  Webhook Relay   │   │
│  │  (Kong)     │  │  Service    │  │  (EventBridge)   │   │
│  └──────┬──────┘  └──────┬──────┘  └────────┬─────────┘   │
│         │                │                    │             │
│  ┌──────▼──────┐  ┌─────▼──────┐  ┌─────────▼─────────┐  │
│  │   Story     │  │  Editorial │  │  Analytics        │  │
│  │   Service   │  │  Workflow  │  │  Pipeline         │  │
│  └──────┬──────┘  └─────┬──────┘  └─────────┬─────────┘  │
│         │                │                    │             │
│  ┌──────▼──────┐  ┌─────▼──────┐  ┌─────────▼─────────┐  │
│  │ PostgreSQL  │  │  Redis     │  │  S3 / Data Lake  │  │
│  │ (Primary)   │  │  (Cache)   │  │  (Media Store)   │  │
│  └─────────────┘  └────────────┘  └──────────────────┘  │
└─────────────────────────────────────────────────────────────┘

Key Components

Component	Technology	Purpose
API Gateway	Kong	Request routing, rate limiting, auth validation
Story Service	Rust + Tokio	Core content CRUD, story versioning, publishing pipeline
CMS	Next.js + Sanity	Editorial dashboard, collaborative editing, workflow
Database	PostgreSQL (primary), Redis (cache)	Story storage, metadata, session management
Analytics	ClickHouse + custom pipeline	Real-time analytics, reader behavior tracking
CDN	CloudFlare	Global edge caching, DDoS protection, SSL
Media Storage	S3 + CloudFront	Image/video hosting, optimized delivery

🌐

Global Infrastructure

Aevum News operates across 4 regions (US-East, EU-West, Asia-Pacific, SA-East) with automatic failover. Average API latency: 45ms globally. Uptime SLA: 99.95%.

Content Pipeline

How stories flow from initial pitch through final publication at Aevum News. The pipeline enforces our editorial standards at every stage.

Pipeline Stages

Flow

PICT → DRAFT → REVIEW → FACT-CHECK → EDIT → PUBLISHED → ARCHIVE
  │       │        │         │          │        │          │
  ▼       ▼        ▼         ▼          ▼        ▼          ▼
 Pitch  Writing  Senior   Multi-Layer  Copy   Live      Retired
 Review  Stage  Editor   Verification  Edit  (with    after 90 days
        &      Approval  (Tier 1+2    pass    analytics
        Filed                sources)              window)

Stage Details

1. Pitch & Filing

Correspondents submit story pitches through the CMS. Each pitch must include: headline proposal, source plan, estimated word count, and priority classification (Breaking, Developing, Feature).

2. Draft Stage

Assigned writer drafts the story in the collaborative editor. The editor auto-tracks source attribution completeness and flags any unattributed claims in real time.

3. Senior Editor Review

A senior editor reviews for: narrative structure, source balance, factual accuracy, and tone. They may request revisions or approve for fact-check.

4. Fact-Checking

A dedicated fact-checker independently verifies every claim against primary sources. Claims that cannot be verified are flagged and must be removed or re-attributed.

5. Copy Edit & Final Approval

Copy editor polishes language, checks style compliance, and ensures all names/titles are correct. Managing editor gives final sign-off.

6. Live Publication

Story is published to the website, API, and distribution channels simultaneously. Real-time analytics begin tracking engagement.

⏱️

Breaking News Override

For breaking news, stages 3–5 may be condensed. However, fact-check is never skipped — it runs in parallel with editing. Breaking stories are published with a [Breaking] tag and later updated as verification progresses.

Verification System

Aevum News' multi-layer verification system ensures every published story meets our rigorous accuracy standards before going live.

Verification Layers

Layer 1 — Automated Screening Active

ML-powered tools scan drafts for unattributed claims, factual inconsistencies, and potential plagiarism. Flags are reviewed by fact-checkers.

Layer 2 — Source Validation Active

Each source is checked against our verified source database. New sources undergo independent background verification before being added.

Layer 3 — Cross-Reference Check Active

Claims are cross-referenced against independent sources, official databases, and previously verified reporting.

Layer 4 — Editorial Review Active

A senior editor with domain expertise in the story's subject area conducts a comprehensive review of arguments, context, and balance.

Layer 5 — Managing Editor Sign-Off Required

Final gate before publication. The managing editor verifies all verification layers are complete and no critical issues remain.

📊

Verification Metrics (Q4 2024)

98.7% first-pass accuracy rate. Average verification time: 4.2 hours for standard stories, 1.8 hours for breaking news. 147 corrections published (0.3% of total output).

Our Team

Aevum News is led by a diverse team of veteran journalists, technologists, and editorial leaders committed to truth-driven journalism.

Leadership

Name	Role	Background
Dr. Elena Vasquez	Editor-in-Chief	Former BBC Foreign Affairs Editor; 20 years in international journalism
Marcus Chen	Chief Technology Officer	Ex-Netflix engineering lead; built real-time systems at scale
Aisha Okonkwo	Head of Editorial Standards	Pulitzer Board member; established fact-checking protocols at The Guardian
David Kimura	Managing Editor	25 years at Reuters; specializes in developing correspondent networks
Sofia Ramirez	Director of Analytics	Ex-Google data science; pioneer in newsroom analytics

Editorial Board

The Aevum News Editorial Board comprises 12 senior journalists from across our global offices. The board meets weekly to set editorial priorities, review controversial stories, and ensure editorial independence is maintained at all times.

Board members are selected for their domain expertise, with coverage spanning geopolitics, technology, economics, science, culture, and human rights.

🤝

Editorial Independence

Aevum News has no corporate owners. We are funded exclusively by reader subscriptions, grants, and ethical partnerships. Our editorial board has veto power over any potential commercial influence on content.

Style Guide

Aevum News style guide — our reference for consistent writing, formatting, and presentation across all content.

Formatting

Element	Rule	Example
Headlines	Title case, max 12 words	`Global Summit Reaches Historic Climate Accord`
Subheads	Sentence case, descriptive	`The agreement covers emissions targets for the next decade`
Body text	Sentence case for all prose	Standard paragraph formatting
Links	Descriptive text, not "click here"	`According to the report, ...` not `Click here for details`
Dates	Month Day, Year (no commas)	`January 15, 2025`
Times	24-hour with timezone	`14:30 UTC`

Commonly Confused Terms

Use	Not	Reason
`bilateral`	`multilateral`	Bilateral = two parties; multilateral = many
`alleged`	`accused`	Alleged is used until charges are filed
`democrat`	`Democrat`	Lowercase for general; capitalize when referring to the US party
`climate change`	`global warming`	Climate change is the broader, scientifically accurate term
`reported`	`claimed`	Reported attributes to a source; claimed implies skepticism

Analytics & Metrics

How Aevum News measures the impact, reach, and engagement of its content.

Key Metrics

Metric	Definition	Measurement
Verified Reads	Reads where >70% of content was viewed	Cookie + session tracking
Time-to-Read Ratio	Percentage of article read by visitor	Scroll depth analysis
Share Rate	Shares per 100 verified reads	Social API integration
Return Reader Rate	Percentage of readers who return within 7 days	Authenticated user tracking
Correction Impact	Reader response to published corrections	Engagement with correction notices

📊

Quarterly Report

A full analytics report is published quarterly and available to all subscribers. It includes trend analysis, regional breakdowns, and methodology documentation.

API Authentication

Aevum News API uses Bearer token authentication. All requests must include a valid API key in the Authorization header.

Obtaining an API Key

1

Register at the Developer Portal

Visit developer.aevumnews.com and create an account using your work email.

2

Verify Your Email

Check your inbox for a verification link. Click to confirm within 48 hours.

3

Generate Your Key

Go to Settings → API Keys and click Generate New Key. Copy and store it securely.

cURL

# Include your API key in every request
curl -X GET https://api.aevumnews.com/v2/stories \
  -H "Authorization: Bearer YOUR_API_KEY_HERE"

🔐

Security Notice

API keys are tied to your account and cannot be recovered if lost. Rotate keys periodically. Never expose keys in client-side code or public repositories. Revoked keys are immediately invalidated.

Organizational Policies

Aevum News governance framework, conflict of interest policies, and ethical guidelines for all team members and contributors.

Conflict of Interest Policy

All Aevum News personnel must disclose any potential conflicts of interest annually and immediately when new situations arise.

Required Disclosures Include:

Personal financial holdings in companies covered by their beat
Family relationships with subjects of reporting
Past employment with organizations relevant to current coverage
Political affiliations or activism related to beat topics
Gifts, travel, or accommodations from any source related to coverage

⚠️

Non-Disclosure Consequence

Failure to disclose a conflict of interest may result in immediate removal from the beat and potential termination. Aevum News maintains a zero-tolerance policy for undisclosed conflicts.

Data Privacy Policy

Aevum News complies with GDPR, CCPA, and all applicable data protection regulations. Reader data is handled per our published Privacy Policy.

Key Commitments:

No sale of reader data to third parties
Anonymous analytics only (no PII in analytics pipelines)
Readers can request data deletion at any time
SSL/TLS encryption for all data in transit
Annual third-party security audits

Code of Conduct

Aevum News is committed to fostering a safe, inclusive, and respectful environment for all team members, contributors, and community participants.

Our Commitments

Respect: Treat every person with dignity regardless of role, background, or opinion
Inclusivity: Actively seek diverse perspectives in reporting, hiring, and leadership
Psychological Safety: No retaliation for raising concerns or reporting misconduct
Professional Boundaries: Maintain appropriate boundaries between professional and personal interactions

Reporting

Violations of this code can be reported through:

Your direct supervisor (if comfortable)
HR at hr@aevumnews.com
Anonymous hotline: +1-800-AEVUM-01
Independent ombuds: ombuds@aevumnews.com

📋

Response Timeline

All reports are acknowledged within 24 hours and investigated within 5 business days. The reporter receives updates throughout the process and a final resolution summary.

Webhooks (Beta)

Receive real-time event notifications from Aevum News. Subscribe to webhooks to get instant updates when stories are published, updated, or corrected.

Available Events

Event	Trigger	Payload
`story.published`	A new story goes live	Story ID, headline, category, timestamp
`story.updated`	A story is significantly updated	Story ID, update summary, previous version hash
`story.corrected`	A correction is published	Story ID, correction text, correction timestamp
`breaking.alert`	Breaking news alert issued	Alert text, severity, affected regions

JSON — Webhook Payload

{
  "event": "story.published",
  "timestamp": "2025-01-15T14:30:00Z",
  "data": {
    "story_id": "ast_9f3d2a1b",
    "headline": "Global Leaders Reach Climate Agreement",
    "category": "world",
    "author": "Elena Rodriguez",
    "url": "https://aevumnews.com/stories/9f3d2a1b"
  }
}

ℹ️

Setting Up Webhooks

Webhooks are in beta. Contact your account manager or email api-support@aevumnews.com to enable webhook access. Each webhook requires a POST endpoint that returns 200 OK within 5 seconds.

API Endpoints Reference

Complete reference for all Aevum News API endpoints, parameters, and response formats.

Stories

GET /v2/stories Stable

Retrieve a list of stories with optional filtering.

Query Parameters

category string Optional

Filter by content category. Accepted values: world, politics, technology, business, science, culture, health, climate.

region string Optional

Filter by geographic region. ISO 3166-1 alpha-2 codes accepted.

date_from date Optional

Start date filter (ISO 8601). Inclusive.

limit integer Optional

Number of results to return. Default: 20. Max: 100.

cursor string Optional

Pagination cursor from previous response.

GET /v2/stories/{story_id} Stable

Retrieve a single story by its unique ID.

Path Parameters

story_id string Required

The unique story identifier (e.g., ast_9f3d2a1b).

Analytics

GET /v2/analytics/{story_id} Beta

Get engagement analytics for a specific story.

Corrections

GET /v2/corrections Stable

Retrieve the public corrections log.

Query Parameters

date_from date Optional

Filter corrections from this date forward.

severity string Optional

Filter by severity: minor, moderate, major, critical.

Changelog

Version history and notable changes for Aevum News platform, API, and documentation.

Version 2.4.1 — January 2025

Added: Webhook event breaking.alert
Added: Analytics endpoint for story engagement metrics
Fixed: Rate limit header parsing for European regions

Version 2.4.0 — December 2024

Added: Webhook beta access for partner accounts
Added: New category filter for climate
Changed: Increased default rate limit from 50 to 100 requests/hour
Deprecated: V1 API endpoints (sunset: March 2025)

Version 2.3.0 — October 2024

Added: Corrections log endpoint /v2/corrections
Added: Cursor-based pagination for story endpoints
Fixed: Timezone handling in story timestamps

Version 2.2.0 — July 2024

Added: Regional filtering support (ISO 3166-1)
Added: Webhook support for story.published, story.updated, story.corrected
Changed: API base URL migrated to api.aevumnews.com/v2

📌

Full Changelog

View the complete changelog on our GitHub Releases page. Major version changes are communicated via our developer newsletter.

Frequently Asked Questions

Common questions about Aevum News operations, API access, editorial policies, and more.

General

What is Aevum News?

Aevum News is a globally distributed digital journalism platform founded in 2022, delivering authoritative, unbiased reporting from correspondents in 120+ countries. Our name reflects our commitment to journalism that endures beyond the daily news cycle.

How is Aevum News funded?

Aevum News is funded exclusively through reader subscriptions, ethical grants, and corporate partnerships that maintain full editorial independence. We have no corporate owners and our editorial board has veto power over any commercial influence.

How can I become a correspondent?

Interested correspondents should submit their credentials and portfolio through our Correspondent Application Portal. We review applications quarterly and prioritize journalists with demonstrated expertise in underrepresented regions and beats.

API & Technical

Is the Aevum News API free to use?

Yes. We offer a free tier with 100 requests/hour, a Partner tier with 10,000 requests/hour, and custom Enterprise plans. All tiers include full read access to our API. See our pricing page for details.

What programming languages do you support?

The Aevum News API is language-agnostic REST API — it works with any language that can make HTTP requests. We also provide official SDKs for Python, JavaScript/Node.js, and Go.

How do I report a bug in the API?

Report bugs via our GitHub Issues page or email api-support@aevumnews.com. Please include the request ID from the response headers in your report.

Editorial

How does Aevum News verify its reporting?

We use a five-layer verification system: automated screening, source validation, cross-reference checks, senior editorial review, and managing editor sign-off. Every factual claim must be attributed to a verifiable source.

How do I submit a correction or feedback?

You can submit corrections through our Corrections Page, via the API endpoint POST /v2/feedback, or by emailing corrections@aevumnews.com. All submissions are reviewed by our editorial team.

Can I republish Aevum News content?

Yes, under our Creative Commons BY-NC-SA 4.0 license for non-commercial use. For commercial syndication, contact our Partnership Team. All republished content must include full attribution and a link to the original.

Support & Contact

Get help from the Aevum News team. We're here to assist developers, partners, and readers.

Contact Channels

📧

General Inquiries

hello@aevumnews.com

Response within 24 hours

🔧

API Support

api-support@aevumnews.com

Response within 4 hours for critical issues

🛡️

Security

security@aevumnews.com

24/7 incident response team

✏️

Editorial

editorial@aevumnews.com

For corrections, feedback, and tips

Community

Developer Forum: forum.aevumnews.com
Twitter/X: @AevumNewsDev
GitHub: github.com/aevumnews
Status Page: status.aevumnews.com

🕐

Support Hours

API support: 24/7 for critical incidents. General support: Mon–Fri, 08:00–20:00 UTC. Weekend support available for Enterprise customers.