Changes to List available user configurations
GET /v1/notifications/configurations
Every recorded change to this endpoint, newest first. Back to the operation
Changed in 5 of the 75 revisions of this API.1373
What changed
- ●
added the new
typeenum value to theallOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterStandard]/ruleresponse property for the response status400response-property-enum-value-added
- ●
- ▲
the response property
allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterChoiceItem]/sourcebecame nullable for the status400response-property-became-nullable
- ▲
the response property
allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterDependentItem]/sourcebecame nullable for the status400response-property-became-nullable
- ▲
the response property
allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterMaximumLength]/sourcebecame nullable for the status400response-property-became-nullable
- ▲
the response property
allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterMinimumLength]/sourcebecame nullable for the status400response-property-became-nullable
- ▲
the response property
allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterStandard]/sourcebecame nullable for the status400response-property-became-nullable
- ▲
the response property
detailbecame nullable for the status401response-property-became-nullable
- ▲
the response property
instancebecame nullable for the status401response-property-became-nullable
- ▲
the response property
statusbecame nullable for the status401response-property-became-nullable
- ▲
the response property
titlebecame nullable for the status401response-property-became-nullable
- ○
the
event_subscription_countresponse's property default value0was added for the status200response-property-default-value-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
for the
queryrequest parameterfilter, the type/format of propertyevent_descriptionwas specialized from/toobject/request-parameter-property-type-specialized
- ▲
for the
queryrequest parameterfilter, the type/format of propertyevent_namespacewas specialized from/toobject/request-parameter-property-type-specialized
- ▲
for the
queryrequest parameterfilter, the type/format of propertyevent_titlewas specialized from/toobject/request-parameter-property-type-specialized
- ▲
for the
queryrequest parameterfilter, the type/format of propertyregionwas specialized from/toobject/request-parameter-property-type-specialized
- ○
the
event_subscription_countresponse's property default value0was removed for the status200response-property-default-value-removed
This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ●
for the
queryrequest parameterfilter, the type/format of propertyevent_descriptionwas changed fromobject/to/request-parameter-property-type-changed
- ●
for the
queryrequest parameterfilter, the type/format of propertyevent_namespacewas changed fromobject/to/request-parameter-property-type-changed
- ●
for the
queryrequest parameterfilter, the type/format of propertyevent_titlewas changed fromobject/to/request-parameter-property-type-changed
- ●
for the
queryrequest parameterfilter, the type/format of propertyregionwas changed fromobject/to/request-parameter-property-type-changed
- ○
the
event_subscription_countresponse's property default value0was added for the status200response-property-default-value-added
- ●
- ●
added the new
cloud-gatewaysenum value to thedata/items/event_namespaceresponse property for the response status200response-property-enum-value-added
- ●
added the new
gateway-managerenum value to thedata/items/event_namespaceresponse property for the response status200response-property-enum-value-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●