Returns the latest chalks each from "right here", "this block", "within two blocks", and "in your neighborhood". Up to 100 results.

Note that the "neighborhood" field/attribute refers not to the neighborhood of a specific chalk but rather to the user's current neighborhood (as determined from the latitude and longitude passed in with the request). This data is not always available but is returned when it is known. In the XML response this it takes the form of a single attribute on the top-level "chalk" tag. In the JSON response it is a field that recurs with each individual chalk; despite this, the field should not be confused as being related to a specific chalk. (This JSON format is admittedly a hack but it was done in order to allow providing this data without breaking backwards compatibility with the current API version. This will be improved in the next version of the API.)

Clients should preserve the order of chalks as provided in the response for end users, which should be considered relevance ranked by the server. Chalks are currently returned in reverse chronological order but this may change with new ranking implementations.

URL:
http://blockchalk.com/api/v0.6/chalks?lat=latitude&long=longitude

If you also provide the optional URL parameter user=userId the results will be filtered to omit any chalks that the given user has buried (see POST /chalk/chalkId/bury).

If you provide the optional URL parameter profanityFilter=true a profanity filter will be applied to the results.

If you provide the optional URL parameter threadId=threadId, results will include all chalks for the threadId and no others, regardless of the query's lat/long coordinates, which are still required. The order of chalks will always contain the first thread chalk as the first in the response, with subsequent comments then in reverse chronological order.

HTTP method:
GET

Formats:
By default results are returned as XML. You can request JSON or RSS by adding the optional &format=xml|json|rss parameter.

Note that threadId and threadCount properties are not returned on RSS format responses.

Response (success): HTTP 200

XML:
<chalks neighborhood="Inner Sunset">
<chalk>
<id>7b1ec33dc010</id>
<contents>Drinking at Gordon biersch</contents>
<datetime>2009-08-14 00:07:04 UTC</datetime>
<distance>right here</distance>
<coordinates lat="37.344" long="-121.888"/>
<place/>
<chalkbackTo>32a9f4ea86a2</chalkbackTo>
<threadId>32a9f4ea86a2</threadId>
<threadCount>2</threadCount>
<category>Chatter</category>
</chalk>
<chalk>
<id>36d9f2ea81a2</id>
<contents>I'm the froyo mayur</contents>
<datetime>2009-08-13 23:09:11 UTC</datetime>
<distance>within a few blocks</distance>
<coordinates lat="37.442" long="-122.159"/>
<place>123 Main St Anytown, CA</place>
<threadId>32a9f4ea86a2</threadId>
<threadCount>2</threadCount>
<category>Chatter</category>
</chalk>
</chalks>

JSON:
[{"contents": "Drinking at Gordon biersch", "neighborhood":"Inner Sunset","id": "7b1ec33dc010", "datetime": "2009-08-14 00:07:04 UTC", "distance": "right here", "chalkbackTo":"32a9f4ea86a2", "coordinates":{"lat":"37.344","long":"-121.888"}, "threadId": "32a9f4ea86a2", "threadCount": "2", "category": "Chatter"}, {"contents": "I'm the froyo mayur", "neighborhood":"Inner Sunset", "id": "36d9f2ea81a2", "datetime": "2009-08-13 23:09:11 UTC", "distance": "within a few blocks", "coordinates": {"lat":"37.443","long":"-122.159"}, "place": "123 Main St Anytown, CA", "threadId": "32a9f4ea86a2", "threadCount": "2", "category": "Chatter"}]

Response (failure): HTTP 400

XML:
<errors>
<error>no latitude</error>
<error>invalid longitude</error>
</errors>

JSON:
[{"error": "no latitude"}, {"error": "invalid longitude"}]