Zapnoty — Authentication

API Documentation

REST API for notifications via Telegram and Max. Subscribers, OTP, broadcasts, forms, helpdesk.

Authentication

All API requests require a Bearer token in the Authorization header.

Base URL: https://api.zapnoty.com
Content-Type: application/json required for all POST/PUT/PATCH requests

Header format:

Authorization: Bearer zn_aBcDeFgHiJkLmNoPqRsTuVwXyZ123456

API key format: zn_ + 32 characters. Keys are created in the project dashboard. Each project has two keys: the live zn_live_ — full access; the test zn_test_ — read-only (GET) plus runtime operations in the sandbox (send, OTP, broadcast, simulate-event), it cannot change project settings (returns 403, see the «Testing» section). Virtual zn_virt_ keys are scoped keys for delegation.

Never pass the key in URL or query parameters. Use only the Authorization header.

Related sections

Quick start
First message in 2 minutes: obtain a key, subscribe via deep link, send via curl.
POST /v1/send — delivery
Send personal notifications: text, HTML/Markdown, media, buttons, templates.
OTP — confirmation codes
Generate and verify 6-digit codes. Dedicated flow for users without a subscription.