Send a push notification from a webhook when a page changes
Map a monitor's headline, content and update id onto a phone message without pasting a diff.
·3 min read
Sending a push notification from a webhook is mostly a translation job: an incoming JSON event becomes a short message with a title. For SEO and content teams the common case is a page-change webhook that needs to reach a phone without anyone watching a dashboard.
The translation problem
A monitor's webhook payload is built for machines. A notification is built for a human glancing at a lock screen. The bridge between them should do four things and no more: verify the sender, pick three fields, trim them and forward.
| Incoming field (AyeWatch example) | Use in the notification |
|---|---|
headline |
the title, trimmed to 100 characters |
content |
the message body, trimmed to 2,000 |
update_id |
the idempotency key |
| quotes with source URLs | a link or a short excerpt |
That mapping is documented rather than guessed: AyeWatch's API reference lists the payload fields, the X-AyeWatch-Signature header and the retry behavior.
Verifying before you trust it matters more than any other step. Each request is signed: the header carries a keyed SHA-256 digest over the bytes that arrived. Recompute it with your secret, check equality without an early exit, and treat a mismatch as a rejection before any decoding happens.
Then acknowledge quickly. A receiver that stalls gets cut off: the reference describes a 10 second ceiling, after which a failing response is attempted again with growing delays, up to ten times in total. Doing the phone send inline is usually fine, but a slow third party is not.
The forward call
The push endpoint takes a bearer token and a short body. Text alone is used as the headline; a JSON object allows a longer body and a colored chip.
curl -fsS https://ayeping.com/@you \
-H "Authorization: Bearer $AYEPING_TOKEN" \
-H "Idempotency-Key: $UPDATE_ID" \
-d "{\"title\":\"Pricing page changed\",\"message\":\"$HEADLINE\",\"label\":{\"text\":\"seo\",\"color\":\"blue\"}}"
Building JSON in shell is fragile. Prefer a tiny script in your language of choice, or a tool such as jq -n with --arg so quotes and newlines are escaped for you.
Why this suits an SEO workflow
Page-change events are bursty. A competitor renames a plan and you get three updates in an hour; then nothing for a week. A phone notification matches that shape better than a dashboard nobody opens, and the message can carry the specific line that moved, such as a new price or a removed feature.
Pair it with a human check on the page before acting. A change event tells you something moved, not whether the movement matters.
What not to put in the message
Keep the notification under the limits and free of anything sensitive. The title allows 1 to 100 characters on one line, the message 2,000, and the whole body 32 KB. A page diff pasted whole will exceed all three.
Also resist sending every event. If a monitor checks a noisy page, filter on the trigger condition before the bridge calls the phone service.
Rate limits worth knowing
Each token allows 1 to 3,600 requests an hour, 60 by default, so a burst of events from a busy page can approach that. The response headers RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset tell you where you stand, and a 429 comes with Retry-After.
Pricing as of November 2026
A trial tier offers five pings and three tokens without payment details. The Hobby tier is billed at $8 monthly, or $49 for a year, with 120,000 pings and 25 tokens included. Pro is $20 monthly or $120 yearly, with 1,200,000 pings and 100 tokens. Leftovers expire rather than bank.
FAQ
Can a page monitor send straight to a phone without a bridge?
Some monitors include push and a feed natively. A bridge is needed when you want the alert in a specific app or a different channel.
What happens if my bridge returns an error?
AyeWatch retries a non-2xx response up to 10 times. Return 2xx once you have stored the event, and process the send from a queue.
How do I avoid duplicate alerts from retries?
Use the event's update id as the Idempotency-Key. A repeat returns the first ping instead of delivering a second.