Ping Us!

Are you posting public events in iCalendar (RFC-2445) format on your website or blog? Enter the information below so your events are indexed by Eventful. This way more people can find out about them!

Your iCalendar file's URL:
Your website or blog TITLE:
Your website or blog URL:
Please don't abuse this service. By using it you agree to Eventful's Terms of Service.

Important note regarding use of this Ping mechanism: we reserve the right to review and exclude from Eventful's index and search results, any information we deem inappropriate for any reason.

Quick! A mini-FAQ:

Q: Do you accept any event data formats besides iCalendar?
A: Not yet, but we will soon! iCalendar support is the first baby step. :-)

Alternative Ping Interfaces

For those who prefer ping us programmatically, you can do so using either of our two ping interfaces, XML-RPC or REST.

REST ping interface
In its GET form, it would look like this:

  http://evdb.com/ping?data_url=AAAAA&attribution_url=BBBBBB&attribution_text=CCCCCC

where AAAAA would be the url pointing to where your iCalendar file can be accessed; BBBBB would be the URL for the page you wish to send people to to find out more information about you (typically this would be your website's or blog's homepage); and CCCCC would be the title of your blog or website to which you're sending users.

We also support POST, with the same arguments, with any of the usual POST encoding schemes.

Several synonyms are supported to make the ping URL shorter, if desired.

Synonyms for the data URL paremeter are: data_url, url, u
Synonyms for the attribution URL parameter are: attribution_url, a
Synonyms for the attribution text parameter are: attribution_text, at

XML-RPC ping interface
To support our friends who may already be doing weblog-style pings, we also support an XML-RPC ping form. The url is the same ("http://evdb.com/ping"), and the XML-encoded request, which is derived from the "extended" weblog ping form is as follows:

<?xml version="1.0"?>
<methodCall>
  <methodName>eventUpdates.ping</methodName>
  <params>
    <param>
      <value>
        <string>YOUR ATTRIBUTION STRING HERE</string>
      </value>
    </param>
    <param>
      <value>
        <string>http://www.YOURATTRIBUTIONURL.com/</string>
      </value>
    </param>
    <param>
      <value>
        <string>http://www.YOURSITE.com/PATH/TO/YOUR/CONTENT</string>
      </value>
    </param>
  </params>
</methodCall>