Twingly RPC Ping API is an XML-RPC API for sending “weblog pings”. It’s designed to work like weblogs.com “reference” API.
If you’d like to manually ping your blog, please use twingly.com/ping.
Please do not abuse the API, you will most likely be blocked (silently). We’re only interested in blogs, so sending us news sites or webshops will also likely cause a block.
Requests should be sent as HTTP POST to https://rpc.twingly.com/ with an XML body.
weblogUpdates.pingName of site (required)URL of site or RSS feed (required)<?xml version="1.0"?>
<methodCall>
<methodName>weblogUpdates.ping</methodName>
<params>
<param>
<value>Twingly Blog</value>
</param>
<param>
<value>http://blog.twingly.com/</value>
</param>
</params>
</methodCall>
weblogUpdates.extendedPingName of site (required)URL of site or RSS feed (required)URL of the post (optional)URL of the feed (optional)A name or tag (optional)<?xml version="1.0"?>
<methodCall>
<methodName>weblogUpdates.extendedPing</methodName>
<params>
<param>
<value>Twingly Blog</value>
</param>
<param>
<value>http://blog.twingly.com/</value>
</param>
<param>
<value>http://blog.twingl.com/new_post</value>
</param>
<param>
<value>http://blog.twingly.com/feed/</value>
</param>
<param>
<value>blog|search</value>
</param>
</params>
</methodCall>
If you’ve sent a valid URL with a correct format, the successful response will look like:
<?xml version="1.0" ?>
<methodResponse>
<params>
<param>
<value>
<struct>
<member>
<name>flerror</name>
<value>
<boolean>0</boolean>
</value>
</member>
<member>
<name>message</name>
<value>
<string>Thanks for the ping.</string>
</value>
</member>
</struct>
</value>
</param>
</params>
</methodResponse>
If you’ve failed, it will look like:
<?xml version="1.0" ?>
<methodResponse>
<params>
<param>
<value>
<struct>
<member>
<name>flerror</name>
<value>
<boolean>1</boolean>
</value>
</member>
<member>
<name>message</name>
<value>
<string>No URL to ping.</string>
</value>
</member>
</struct>
</value>
</param>
</params>
</methodResponse>
rpc.twingly.com can now be used over HTTPS