API v1

Added Contacts

A contact carries its age and next birthday

A contact now holds age, in whole years on the key owner's current day, and next_birthday_on, the next birthday written Y-m-d. Both are null when the birthday is not recorded, and age is also null when its year or month is unknown. Both are null for a sensitive birthday read without the sensitive-fields ability.

Why it changed

A client had to work the age and the coming birthday out from the birthday field, and could not agree with the contact page on the day.

Changes

In the same release