API Documentation
Everything you need to integrate Pager.Quest into your workflow.
Overview
Pager.Quest provides API endpoints to send push notifications to yourself via Telegram or Email.
https://api.pager.quest/telegramhttps://api.pager.quest/emailPOSTAuthentication
All requests require a Pager.Quest API key sent via the Authorization header:
Telegram API key — message @PagerQuestBot on Telegram. The bot will generate and send you a unique key automatically.
Email API key — get your Email API key here. Alternatively, send /link_email to @PagerQuestBot, then reply with your email address. Your Email API key will be sent to that address.
Send Text Notification
Send plain text directly in the request body. No JSON wrapper needed. Works for both /telegram and /email.
Alternatively, send structured JSON with an optional title field:
(note: title only works for Email notifications)
Send Image Notification
Send an image by providing a URL or Base64-encoded data. Delivered as a photo in Telegram, or an email attachment.
Send File Notification
Send any file by providing a URL or Base64-encoded data. Delivered as a document in Telegram, or an email attachment.
Response Codes
| Code | Description |
|---|---|
200 | Notification sent successfully |
400 | Invalid request — missing/invalid API key, empty body, bad JSON, or no email linked |
404 | Invalid API endpoint |
405 | Method not allowed — only POST is accepted |
429 | Rate limit exceeded — retry after the specified time |
502 | Failed to send notification (Telegram or Email delivery error) |
Rate Limits
| Channel | Plan | Per Minute | Per Day |
|---|---|---|---|
| Telegram | Free | 1 notification | 10 notifications |
| Telegram | Paid Member | 100 notifications | Unlimited |
| Free | — | 5 notifications | |
| Paid Member | — | 100 notifications |
When rate-limited, you'll receive a 429 response with a Retry-After header indicating the wait time in seconds.