API & Rate Limits
Rate limits depend on your subscription tier:
- Developer (Free): 100 requests/hour, 10 concurrent connections
- Pro: 5,000 requests/hour, 50 concurrent connections
- Enterprise: 50,000+ requests/hour, unlimited concurrency (custom SLA)
Exceeding limits returns a 429 Too Many Requests response with a Retry-After header. Monitor your usage via the Developer Dashboard.
Yes. Webhooks are available on Pro and Enterprise plans. Configure endpoints via the dashboard or use the /v2/webhooks API. Payloads include full article metadata, category tags, and source verification hashes. All webhook deliveries are signed with your secret key for integrity verification.
Use the /v2/archives endpoint with date range parameters (start_date, end_date). Historical data is available back to 2018 for standard feeds, and 2012 for Enterprise clients with legacy archive access. Results are paginated (max 100 items/page) and can be filtered by region, topic, or source credibility score.
Authentication & Security
All requests require a valid Bearer token in the Authorization header:
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6...
Tokens expire after 24 hours. Use our OAuth 2.0 client credentials flow for server-to-server authentication. API keys can be rotated anytime from the security settings panel without downtime.
Yes. Navigate to Settings → Security → IP Allowlisting to restrict API access to specific CIDR ranges. This is recommended for enterprise deployments. Changes propagate within 60 seconds. Note: IP whitelisting does not replace token authentication.
Absolutely. We operate as a data processor and never collect personal identifiable information (PII) from end-users. All data transfers are encrypted in transit (TLS 1.3) and at rest (AES-256). We provide Data Processing Agreements (DPA) upon request and support regional data residency options for EU and APAC deployments.
Data Feeds & Integration
We support:
- JSON (default): Structured, nested metadata with strict schema validation
- XML: Legacy system compatibility with XSD schemas provided
- RSS 2.0 / Atom: Public feed endpoints with configurable refresh intervals
- CSV: Batch export for analytics and archival (Enterprise only)
Specify your preferred format via the Accept header or ?format= query parameter.
Corrections and retractions are flagged with a correction_status field in the payload. When an article is updated, the system pushes a TYPE: UPDATE webhook with version diff metadata. Retracted articles receive a retraction_notice object and are automatically excluded from active feeds unless you enable the ?include_retractions=true parameter for archival purposes.
Yes. Every article includes a source_score (0.0–1.0) and editorial_tag (e.g., "verified", "opinion", "satire", "preliminary"). Use query parameters like ?min_score=0.85 or ?tags=verified,hard-news to filter. Our credibility engine updates daily using multi-factor verification including cross-source validation and historical accuracy tracking.
Troubleshooting & System Status
Common causes:
- Expired or invalid API token
- IP address blocked due to rate limiting or suspicious activity
- Attempting to access Enterprise-only endpoints on a lower tier
Verify your token at api.aevumnews.com/v2/validate. If the issue persists, check your dashboard alerts or contact support with your request ID.
Visit status.aevumnews.com for live metrics, historical uptime reports, and incident logs. You can subscribe to RSS alerts or webhook notifications for automatic updates when endpoints experience degradation or maintenance windows.
File a ticket via the Developer Portal or email devsupport@aevumnews.com. Include your API key (last 4 characters), endpoint, payload sample, and expected vs actual response. Enterprise clients receive dedicated Slack channels and priority response times (< 4 hours).