Why did new payload fields break my parser?
New fields can appear in payloads as part of normalised-schema updates.
New fields can appear in payloads as part of normalised-schema updates. These additive changes are treated as backward-compatible and may not be announced in advance, since the wire format is kept additive-only. They arrive with null values where not yet computed.
Configure your deserializer to allow (ignore) unknown fields rather than reject the whole payload.
Rely on the webhook signature to authenticate that the payload came from Terra.
New fields are also reflected on the docs changelog.
PreviousWhy does Oura app HRV differ from the API HRV?
NextWhy are COROS activities delayed by several minutes?
Last updated
Was this helpful?