# A contact carries its age and next birthday

20 November 2026 · Added · Contacts

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

- `age` (Added): `GET /api/v1/vaults/{vault}/contacts`, `GET /api/v1/vaults/{vault}/contacts/{contact}`
- `next_birthday_on` (Added): `GET /api/v1/vaults/{vault}/contacts`, `GET /api/v1/vaults/{vault}/contacts/{contact}`

## In the same release

- Changed: [Your contact starts on the template you choose](https://my.monicahq.com/docs/api/changelog/vault-create-owner-on-chosen-template.md)
- Changed: [Last in touch is recorded](https://my.monicahq.com/docs/api/changelog/last-interaction-at-recorded.md)
- Changed: [A number field refuses a number it cannot hold](https://my.monicahq.com/docs/api/changelog/number-field-range.md)
- Changed: [The last contact template stays](https://my.monicahq.com/docs/api/changelog/template-destroy-last-contact-template.md)
