Loading ...
Sorry, an error occurred while loading the content.

Re: Address Book API vs. Contacts API

Expand Messages
  • danteifke
    Thanks for the feedback Craig, I ll probably take your advice and start with the AB API, but keep an eye on the Contacts API. One final question. It looks
    Message 1 of 5 , Apr 23, 2009
    • 0 Attachment
      Thanks for the feedback Craig,
      I'll probably take your advice and start with the AB API, but keep an eye on the Contacts API. One final question. It looks like Contacts API only has READ operations, while the AB API has UPDATE capabilities. Am I understanding this correctly?
      Thanks,
      Dan


      --- In ydn-addressbook@yahoogroups.com, Craig Wright <crw@...> wrote:
      >
      > Howdy Dan,
      > The Contacts API is the newer, Y!OS-style API, which will someday replace what is called the Address Book API. As such it should eventually be more fully integrated with the other social features in Y!OS, and follows the format conventions of Y!OS.
      >
      > The "Address Book" API is the API which is fully implemented and in use by several large-scale integrators today. I am not sure what the roadmap is for the Contacts API, but at the moment it does not have feature-parity with the Address Book API. AB API has its own format and unfortunately will probably not be upgraded for use with OAuth (although I would love to see this happen).
      >
      > Yahoo! Address Book was rebranded Yahoo! Contacts a while back. So the APIs are named as you see above based on when they were conceived.
      >
      > Depending on how much time you have, I would suggest starting with the AB API, but realize that you will eventually have to upgrade to the Contacts API when it is up-to-speed and we deprecate the AB API. Unless I am mistaken there are currently no sync operations in the Contacts API.
      >
      > HTH,
      >
      > Craig Wright
      > Front-end Engineer, Yahoo! Address Book
      > http://address.yahoo.com/
      >
      >
      > >
      > >From: danteifke <danteifke@...>
      > >To: ydn-addressbook@yahoogroups.com
      > >Sent: Wednesday, April 22, 2009 3:40:10 PM
      > >Subject: [ydn-addressbook] Address Book API vs. Contacts API
      > >
      > >
      > >
      > >
      > >
      > >I'm just getting started with a potential application that will need access to the Yahoo! Address Book and/or Contacts information (is there a difference?) . Reading through YDN, I see there is an Address Book API and a Contacts API. I'm wondering why I would choose one over the other. One of the of the aspects of my application is the ability to cache a user's address book in my application and then "sync" as needed to Yahoo! The sync operation is preferably a net change type of operation as opposed to re-getting the entire address book. I see that the Address Book API has a sync'ing capability based on a revision number. I can't find any such capability in the Contacts API.
      > >
      > >>I also see that the Address Book API uses BBAuth while the Contact API uses OAuth.
      > >
      > >>Can somebody give me a quick rundown of the reason for choosing one of these API's over the other? Maybe there's link to a side-by-side comparison.
      > >
      > >>I've also posted this question to the YDN Forums / Y!OS / Contacts
      > >
      > >>Thanks,
      > >>Dan
      > >
      > >
      > >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.