Section 01
Documentation
The conceptual model behind Mijorsoft Notifier. Read this once and the rest of the API reference will feel obvious.
Overview
Mijorsoft Notifier is a multi-channel delivery platform. You send a single request to our REST API and we fan it out to Email, Push and In-App channels — each with its own delivery guarantees, retries and observability.
Base URL
https://api.mijorsoft.com/api/v1
Versioning
URI-versioned — /api/v1/...
Content type
application/json
Architecture
Every request passes through four layers. Understanding them helps you reason about latency, retries and failures.
1. Edge & authentication
TLS termination, IP allowlist validation and API key authentication. Rejected requests never reach the pipeline.
2. Routing & validation
Payload schema validation, channel resolution and idempotency key handling. Errors here surface as HTTP 4xx.
3. Channel workers
Independent workers per channel handle provider-specific delivery, retries and rate limits.
4. Events & webhooks
Delivery events are emitted to your webhook endpoints and queryable via the API.
Environments
Every project ships with two fully isolated environments. Keys, data, templates and webhooks never cross between them.
Development
mn_test_...Isolated sandbox. Safe for experiments, test data and CI.
Production
mn_live_...Live traffic. Strict IP allowlist and full audit logging.
API keys
Keys are scoped to a single organization, project and environment. Treat them as server secrets — never ship them to a browser or mobile app.
Server secret only
Never expose an API key in browser JavaScript, mobile applications, public repositories, logs or screenshots.
Rate limits
Limits apply per API key, not per IP. Exceeded requests return HTTP 429 with a Retry-After header.
Default
300 req / min / key
Burst
60 req / 10 s
Notification batch
100 recipients / request
Capabilities
Live availability of each channel and platform feature.