PushizoDocs

Pushizo documentation

Pushizo developer documentation — getting started, channel, SDK, API and operations guides for the multichannel push, email, SMS, WhatsApp, RCS, in-app notification and customer engagement platform.

Pushizo is a notification platform that offers a concept model and SDK surface compatible with your legacy provider, and it can also run on your own infrastructure: push (iOS APNs, Android FCM, Huawei HMS, Web Push), email (SMTP, Amazon SES, Resend), SMS (Twilio, Netgsm), WhatsApp, RCS, in-app messages and the notification inbox; plus segments, Liquid templates, campaigns, A/B tests, journeys, webhooks and analytics.

Sections

Getting started

Concepts, quickstart and per-platform setup (web, iOS, Android, Flutter, server); plans and quotas.

Channels

Web Push, iOS, Android, Huawei; email and deliverability; SMS, WhatsApp, RCS; in-app, notification inbox, Live Activities.

Users & segments

Identity model (user, alias, subscription), tags/properties, segment condition language, preferences, suppression list, KVKK.

Messaging & campaigns

Multichannel content, targeting, scheduling, campaigns, templates, Dynamic Content and the AI assistant.

Journeys

Event- and segment-triggered journeys: 13 node types, waits, conditions, splits, goals, versioning.

A/B testing

Campaign, journey and in-app variants; holdout, significance, automatic winner.

Analytics & data

Reports, Event Streams, data warehouse export, CSV export/import.

Integrations

Segment, Amplitude, Mixpanel, Zapier, Slack, WordPress, WooCommerce, Shopify, GTM, MCP server; React, Vue, Angular.

SDKs

Web, iOS, Android, Flutter, React Native, Capacitor, Cordova, MAUI, Unity; Node, PHP, Python, Go, Java, .NET, Ruby.

API reference

Authentication, scopes, rate limits, idempotency, pagination; every operation and schema by tag.

Webhooks

Event types, Pushizo-Signature verification, secret rotation, retries and replay.

Security & compliance

KVKK/GDPR, data residency (EU/TR), SSO/SCIM, API keys, bot protection, white-label.

Operations

Installation with Docker Compose and Helm, backup/restore, status and monitoring, DMARC, runbooks.

Migration

Moving to Pushizo from your existing platform and Firebase (FCM) setups.

Error catalog

HS_* codes, HTTP statuses and what to do.

Recent updates

vYayınlanmamış
  • Kullanım Şartları yeniden yazıldı (tr/en): ticari kullanım beyanı, müşteri yükümlülükleri, ücret ve iade, garanti reddi, sorumluluk sınırı, tazmin, askıya alma ve…
  • Gizlilik Politikası ve KVKK Aydınlatma Metni: Google/Apple/GitHub ile girişte işlenen veriler, oturum kaydı, veri ihlali bildirimi, başvuru süresi (30 gün) ve panelden…
  • Google ve Apple ile giriş, panel ve API ayrı alan adlarındayken oturum açmıyordu (ADR-0096 eki).
  • Kurumsal SSO (SAML/OIDC) girişi de aynı nedenle oturum açmıyordu; IdP'deki adresler değişmeden düzeltildi (ADR-0096 eki).
  • Tanıtım sitesinde sözleşme sayfaları (Kullanım Şartları vb.) yenileme süresinden sonra 404 veriyordu: üretim sunucusu depo kökünden çalıştığı için içerik dizini…

Core concepts

ConceptDescription
OrganizationThe tenant your account runs in; members, roles, billing and API keys belong to the organization.
App (app_…)The product you send notifications for. Channel credentials, users, subscriptions, segments and campaigns belong to the app. Client SDKs work with the App ID only.
API key (hs_live_…)Server-side access; scoped (notifications:write, users:read, users:write, events:write, segments:read, analytics:read, mcp:write, admin). Never embed it in a client.
User (usr_…, external_id, aliases)Your user; can have multiple subscriptions. login(externalId) links an anonymous device to the user.
Subscription (sub_…)A single channel endpoint: a device token, browser subscription, email address or phone number (ios_push, android_push, hms_push, web_push, email, sms, whatsapp, rcs).
Tag / property / eventSegmentation and personalization data; events feed journey and in-app triggers as well as conversion attribution.
Message (msg_…) and delivery (dlv_…)POST /v1/notifications creates a message; for each recipient subscription, a delivery record carries the queued → sent → delivered/received → opened/clicked timeline.

Endpoints

SurfaceAddress
Application (dashboard)https://app.pushizo.com
Public REST APIhttps://api.pushizo.com/v1 (interactive docs)
Documentationhttps://docs.pushizo.com
Status pagehttps://status.pushizo.com

If you self-host, the addresses depend on your installation (Operations); in the SDKs they are set with apiUrl / baseUrl.

On this page