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. Live zn_live_ keys grant full access — a project can have several (up to 10), each created and revoked individually. The test zn_test_ key — 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.

Temporary keys: when creating a live key you can set an expiry — quick presets (1 hour, 3 hours, 12 hours, 24 hours, 2 days, 3 days) or a custom date. Once the date passes, the key stops authenticating automatically (401), no manual revocation needed. Handy for CI, contractors and one-off integrations. Revoking any key takes effect immediately and does not affect the project's other keys.

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

Related sections