Hey everyone,

I wanted to let you know about a couple of changes we're rolling out for the
API.

1. There will be a new attribute of parentid in the responses from
/1/trends/available.format . This attribute corresponds to the woeid of the
place within which this location is found. In the example San Francisco's
parentid is 23424977, which corresponds to the USA. If the location does not
have a parent (e.g. the world), the parentid will not be included.

XML sample
<location>
  <woeid>2487956</woeid>
  <name>San Francisco</name>
  <placeTypeName code="7">Town</placeTypeName>
  <country type="Country" code="US">United States</country>
  <url>http://where.yahooapis.com/v1/place/2487956</url>
  <parentid>23424977</parentid>
</location>

JSON sample
[
  {
    "name": "San Francisco",
    "woeid": 2487956,
    "placeType": {
      "name": "Town",
      "code": 7
    },
    "country": "United States",
    "url": "http://where.yahooapis.com/v1/place/2487956";,
    "countryCode": "US",
    "parentid": 23424977
  }
]


2. Later this week we will add the error message "Timestamp out of bounds"
to help diagnose issues with your OAuth requests. This error message will be
returned if the oauth_timestamp you send is not within the allowed time skew
of our servers. As a reminder our server time is always included in the HEAD
of our API responses and is in GMT.

3. You may also notice some other API bugs being resolved over the next few
days/weeks. If you've had some workarounds in place, or are just interested,
you may want to keep an eye on the recently closed issues list:

http://code.google.com/p/twitter-api/issues/list?can=1&q=status:Fixed%20OR%20status:Resolved%20type=Defect&sort=-modified


Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to