One API. Three platforms. Zero config hell.
Start with credits, subscribe when it saves money.
curl -X POST https://api.kimepush.kimevik.com/v1/notify \
-H "Authorization: Bearer pk_live_xxxxx" \
-H "Content-Type: application/json" \
-d '{
"to": "user_123",
"title": "Your order shipped",
"body": "Arrives Thursday"
}'{
"notification_id": "notif_01h3n...",
"deliveries_queued": 3,
"devices": [
{ "token_id": "tok_a1b2", "platform": "fcm", "status": "queued" },
{ "token_id": "tok_c3d4", "platform": "apns", "status": "queued" },
{ "token_id": "tok_e5f6", "platform": "web", "status": "queued" }
]
}The 2-4 weeks of infrastructure work. Done.
POST to /v1/notify. We fan out to FCM, APNs, and Web Push in parallel — one response either way.
Stale tokens, reinstalls, and platform-reported errors are cleaned up automatically. Your DB never accumulates dead tokens.
Notify one user or fan out to a whole topic segment — same API, same delivery guarantees either way.
Set scheduled_at and we deliver it later. No cron job to write, no worker to babysit on your end.
Reusable templates with {{variables}} — publish once, send by ID from your backend.
Exponential backoff on every send, plus one-click replay for anything that failed.
Every send's outcome, per device — queued, delivered, failed, and why.
Real-time callbacks for delivery and error events, so you're not polling for status.
Idempotency-Key header for safe retries, plus separate Dev/Test/Prod keys per project.
Sign in with Google. Create a project for your app in 30 seconds.
Drop your Firebase JSON and APNs .p8 file. We encrypt and store them.
One npm install in your mobile app to register device tokens.
One API call. That's it. No FCM auth setup. No APNs JWT rotation.
Use pay as you go for a lean start, or choose a subscription when predictable limits fit better.