Smohix Own API

Who it is for

Integrators and platform engineers connecting billing, ingest, and webhooks.

What works today

• ·Public API catalog at /docs/api
• ·API keys and alert ingest tokens
• ·PayPal webhook sync and proxy routes

Problem

Billing, ingest, and automation callers need stable, documented endpoints — not ad-hoc URLs per service.

Solution

Smohix Own API (documented at /docs/api) exposes cataloged routes; optional REACT_APP_SMOHIX_OWN_API forwards billing events to your centralized service.

How it works

1. Public catalog lists authenticated and webhook routes.
2. API keys and alert ingest tokens scoped per workspace.
3. Same-origin proxies reach private Railway backends.
4. PayPal webhooks sync subscriptions and balance server-side.

Benefits

• ·One reference for integrators and internal teams
• ·Private network URLs never shipped to the browser
• ·Idempotent webhook delivery tracking

Roadmap

• →Expanded Own API event types for cross-product billing
• →SDK documentation alongside the catalog