The WWDC Parties API returns data in only a single format: JSON.
#Example Party

{
    "approved": false,
    "description": "<p>Visit <a href=\"https://www.eventbrite.com/e/5by5-wwdc-2014-meetup-tickets-11485969845\">Eventbrite</a> for more info.</p>",
    "end_time": 1401771600,
    "event_url": "https://www.eventbrite.com/e/5by5-wwdc-2014-meetup-tickets-11485969845",
    "excerpt": "Hang out with fellow listeners and meet the hosts of your favorite 5by5.tv podcasts while enjoying free food and drinks at New Relic's beautiful San Francisco office.",
    "location": "New Relic",
    "meta": {
        "booze": true,
        "cost": "rsvp",
        "food": true
    },
    "name": "5by5 Meetup",
    "shortcode": "50f673",
    "slug": "5by5-meetup",
    "sponsor_name": "New Relic",
    "sponsor_url": "http://newrelic.com",
    "start_time": 1401764400,
    "street_address": "188 Spear Street",
    "twitter_handle": "5by5",
    "type": "party",
    "types": [
        "party"
    ]
}

Form Fields


`approved`	A Boolean value describing whether or not the party has been approved by the WWDC Parties admins. Parties are approved manually to prevent spam, incorrect information, and abuse of the WWDC Parties website. Unapproved parties will not appear on the main website, and will not appear in the "List Parties" endpoint.
`description`	The full description of the party that appears on the party's page on the website. HTML. Sanitized. Hopefully.
`end_time`	The time the party is over and you tell everyone to go home. Number of seconds since the UNIX epoch. Integers only, we aren't ending any parties on millisecond boundaries.
`event_url`	A URL where people can go find more information about the party, RSVP, buy tickets, etc.
`excerpt`	A short (200 characters or less) description of the party that appears on the main page of the website.
`location`	The name of the establishment where the party is taking place. Usually this is a bar or a restaurant, or some company's office. Sometimes people don't list locations, which is weird, because like, there's a street address. This party is happening somewhere. Is it just in the middle of the road? On the sidewalk? Who knows. Anyway, this info may not be here, plan accordingly.
`meta`	A JSON object containing five Boolean keys: 18+: When true, the party will be off limits to anyone under the age of 18. 21+: When true, the party will be off limits to anyone under the age of 21. booze: When true, the party will be serving alcohol, free or otherwise. food: When true, the party will be serving food, free or otherwise. ticket: When true, the party requires a ticket, RSVP, or invitation.
`name`	The name of the party. We try to keep it short, but some people are ridiculous.
`shortcode`	A long, long time ago in a state that isn't the state I live in now, I was planning on adding short URLs for better use in printing and tweeting and whatnot. This is the 6-digit (shut up, hex digits are digits, too) code that would have appeared in the shortened URLs. Currently unused, but if you want to use them, they're another unique identifier for a single party.
`slug`	A unique identifier for the party. Used to generate the URLs both in the API and on the website.
`sponsor_name`	The name of the company or individual that is sponsoring the party.
`sponsor_url`	A URL to a website representing the company or individual that is sponsoring the party.
`start_time`	See `end_time`, but, like, the opposite of that.
`street_address`	The street address where the party is taking place. Only the street address. Not included: the city, state, or ZIP code. City and state can be assumed to be "San Francisco, CA". ZIP code can be assumed to be of no importance, I'm hoping you aren't using this to mail letters. (But seriously, if you need ZIP codes, we can probably work out a thing. I think the USPS has an API or something.)
`twitter_handle`	Twitter username. Without the @-sign. That's really not technically part of your Twitter username anyway. You should know these things.
`type`	"party". Always this says "party". If it doesn't say "party", something has gone horribly wrong. It's just, it's a database thing, okay? Get off my back.
`types`	An array of event types. Can be any combination of: party: Your standard, run-of-the-mill party. meetup: Casual hangouts, BOF events, etc. presentation: Something will be presented. People are expected to watch somebody or something central to the event. outdoors: Not just "taking place outdoors" (bar patios don't count), but an outdoorsy type of event. Hikes, bike rides, photo walks, etc.