PubSub ping service
Tell PubSub when your weblog changes. Send an XML-RPC POST to either endpoint:
Use Content-Type: text/xml. Replace the example name and URLs with your own.
XML-RPC ping
weblogUpdates.ping takes your weblog's name and homepage URL:
<?xml version='1.0'?> <methodCall> <methodName>weblogUpdates.ping</methodName> <params> <param> <value><string>Example Blog</string></value> </param> <param> <value><string>https://example.com/</string></value> </param> </params> </methodCall>
XML-RPC extended ping
weblogUpdates.extendedPing takes the name, homepage URL, changes URL
(often the homepage again), and feed URL, in that order:
<?xml version='1.0'?> <methodCall> <methodName>weblogUpdates.extendedPing</methodName> <params> <param> <value><string>Example Blog</string></value> </param> <param> <value><string>https://example.com/</string></value> </param> <param> <value><string>https://example.com/</string></value> </param> <param> <value><string>https://example.com/feed.xml</string></value> </param> </params> </methodCall>
A successful XML-RPC call returns a struct with flerror set to false
and message set to Thanks for the ping.
REST / GET ping
You can also send a GET request with URL-encoded name and url
parameters, and optionally changesURL as a feed discovery hint. For example:
https://xping.pubsub.com/ping/
?name=Example%20Blog
&url=https%3A%2F%2Fexample.com%2F
Join these lines into one URL. A GET ping replies Thanks for the ping.
Rate policy
Direct senders may send up to 60 requests per minute per address. Pings above the limit are discarded, even though the reply is unchanged. Relays can arrange a higher per-address limit; write to info@pubsub.com.
What happens to a ping?
PubSub checks each ping for spam and valid public URLs. For a new site, PubSub finds its feed, admits the site and fetches the feed, subject to feed validation, robots rules and crawl politeness. A ping for a known site schedules its feed for a fresh fetch.
Contact
Write to info@pubsub.com.
