Just thought you should know that there are some breaking changes coming to cipher API models.
Cipher.Login.Uri on the request and response models is being deprecated in favor of Cipher.Login.Uris, an array of { "Uri": string, "Match": enum }
The cipher response model is being updated to better match the request model. Namely:
Data prop is being deprecated.
Adding: Name, Notes, and Fields to the root object.
Adding: Login, Card, Identity, and SecureNote to the root object (their prop values were part of the dynamic Data property in the past).
Our API will handle these changes in a backwards compatible way for a few iterations since outdated client apps will still be expecting the old models for some time.
These changes are already in the Core API project and refactoring is being done in all client apps over the next few days.
Just thought you should know that there are some breaking changes coming to cipher API models.
Cipher.Login.Uri
on the request and response models is being deprecated in favor ofCipher.Login.Uris
, an array of{ "Uri": string, "Match": enum }
Data
prop is being deprecated.Name
,Notes
, andFields
to the root object.Login
,Card
,Identity
, andSecureNote
to the root object (their prop values were part of the dynamicData
property in the past).Our API will handle these changes in a backwards compatible way for a few iterations since outdated client apps will still be expecting the old models for some time.
These changes are already in the
Core
API project and refactoring is being done in all client apps over the next few days.