Server-side quickstart
Create an API key, send your first POST /v1/notifications request with cURL, then use one of the server SDKs (Node, PHP, Python, Go, Java, .NET, Ruby).
All server-side operations go through the REST API under https://api.pushizo.com/v1; the server SDKs wrap the same API as resource × method. Never embed the API key in a client (browser, mobile app).
Create an API key
Dashboard → Organization → API keys → New key: name, app (or org-wide), scopes (start with notifications:write), optional IP allowlist and expiry date. The raw key (hs_live_…) is shown only once; environment: test keys get the hs_test_ prefix and keep staging integrations separate. Scopes and rotation: API keys.
First request (cURL)
curl -X POST "https://api.pushizo.com/v1/notifications" \
-H "Authorization: Bearer $PUSHIZO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: ilk-bildirim-1" \
-d '{
"app_id": "app_…",
"target": { "test_devices_only": true },
"headings": { "tr": "Merhaba", "en": "Hello" },
"contents": { "tr": "Pushizo çalışıyor", "en": "Pushizo is working" },
"url": "https://pushizo.com"
}'
# 202 → { "id": "msg_…", "status": "queued", "recipients_estimate": 1, "external_id_missing": [] }Status: GET /v1/notifications/{message_id}?app_id=app_…; deliveries: GET /v1/notifications/{message_id}/deliveries. A 202 response means asynchronous delivery; results land in the counters and in webhooks.
Choose an SDK
import { Pushizo } from '@pushizo/node';
const hs = new Pushizo({ apiKey: process.env.PUSHIZO_API_KEY!, appId: 'app_…' });
const res = await hs.notifications.create({
idempotency_key: 'order-1001',
target: { include_aliases: { external_id: ['user_42'] } },
contents: { tr: 'Siparişiniz kargoya verildi', en: 'Your order shipped' },
});All SDKs retry 429/5xx with exponential backoff, generate the idempotency key automatically, and walk cursor pagination with the paginate / list_all / ListAll helpers. Guides: SDKs.
Receive webhooks
Use Dashboard → Developer → Webhooks to receive delivery.*, subscription.* and user.* events on your HTTPS endpoint; verify the Pushizo-Signature header (Webhooks).
Next steps: Sending notifications, User and subscription management, API reference.
React Native, Capacitor, Cordova, MAUI and Unity
Common setup order and platform-specific guides for the bridge SDKs that wrap the native Android/iOS SDKs.
Billing, plans and quotas (Phase 13)
Plan matrix, trial, Stripe/iyzico/mock providers, usage report, quota and feature gates, alert emails. Design decisions: ADR-0020. Shared code: packages/billing (plan matrix, provider adapters, quota…