Webhooks, APIs, and Automation: How Newsroom AIOS Connects to Everything

Newsroom AIOS is built API-first, meaning every function of the platform — from article generation to payment processing to subscriber management — is accessible through structured API endpoints. For publishers who want to automate their operations or integrate with external tools, this architecture opens up powerful possibilities.

The API Architecture

The platform exposes RESTful API routes organized by domain:

• /api/ai/* — Content generation, image search, article creation
• /api/stripe/* — Payment processing, subscription management, invoicing
• /api/credits/* — Usage tracking, balance checks, credit deductions
• /api/tenants/* — Newspaper configuration, deployment, domain management
• /api/scheduled/* — Automated content runs, backup operations

Every API endpoint uses standard authentication: tenant API keys for newspaper-specific operations and platform secrets for administrative tasks.

Stripe Webhook Integration

Payment automation is critical for a newspaper business. The platform's Stripe integration handles the full lifecycle:

• Subscription created — when a new subscriber signs up, the webhook triggers account provisioning and welcome email
• Payment succeeded — monthly subscription renewals are processed automatically with receipt delivery
• Payment failed — automatic retry logic with grace periods before access revocation
• Subscription canceled — graceful offboarding with data export options

For advertising payments, the same webhook architecture handles one-time purchases, recurring ad campaigns, and credit-based billing — all without manual intervention.

Automated Content Scheduling

The /api/scheduled/* endpoints power the platform's automated content pipeline. Publishers can configure:

• Daily article generation — AI journalists produce articles on a schedule, queued for editorial review
• Batch processing — generate multiple articles across categories in a single automated run
• Multi-tenant orchestration — the platform can trigger content generation across all newspapers simultaneously

This is powered by the credit system, which tracks AI usage per tenant. Each operation (article generation, image search, fact-check, SEO optimization) costs a defined number of credits. The system checks credit balance before executing and deducts upon completion — preventing overuse while allowing publishers to manage their monthly budget.

The Credit System API

The credit system is itself a well-designed API layer:

• Balance check (/api/credits/balance) — returns current credits, cycle dates, and usage percentage
• Pre-flight check (/api/credits/check) — validates whether a specific operation can be performed given the current balance
• Deduction (/api/credits/deduct) — atomically deducts credits and logs the transaction

Credit costs are transparent: article generation = 5 credits, image search = 2 credits, fact-checking = 2 credits, SEO optimization = 3 credits, web research = 1 credit. Plans include Starter (250 credits/month), Growth (575), and Professional (1,000).

Deployment Automation

When a new newspaper is provisioned, the platform's deployment API handles the entire chain:

1. Vercel project creation with linked GitHub repository
2. Environment variable injection — 21 configuration values pushed to the deployment
3. Custom domain registration with automatic SSL provisioning
4. Initial content seeding — 36 articles and 100 directory listings generated in parallel
5. Status tracking via real-time Firestore updates that the publisher can monitor

The entire process is triggered by a single API call and monitored through a status page that updates in real time. The publisher sees each step completing — deploy, seed, configure — without needing to understand any of the underlying technology.

CI/CD Pipeline

Code updates to the platform flow through a three-stage CI/CD pipeline:

1. Build validation (ci.yml) — every push triggers a full build to catch errors before merge
2. Version tagging (release.yml) — manual version bumps create GitHub releases with changelogs
3. Tenant rollout (tenant-rollout.yml) — code updates are automatically deployed to every live newspaper

This means every newspaper on the platform gets the latest features, security patches, and performance improvements automatically — without publisher involvement. Ship once, deploy everywhere.

Why API-First Matters

For most publishers, these APIs run invisibly in the background. You don't need to know about webhooks or REST endpoints to run your newspaper. But the API-first architecture matters for three reasons:

• Reliability — automated systems don't forget, don't get tired, and don't make data entry errors
• Scalability — the same automation that serves 10 newspapers serves 1,000 with no changes
• Extensibility — as new features are built (podcasting, social media scheduling, CRM integrations), they plug into the same architecture

The goal is simple: publishers should spend their time on community and content, not on technology. Every API endpoint, every webhook, every automation exists to make that possible.