Changes to Update an DNS Monitor

PUT /v1/checks/dns/{id}

Every recorded change to this endpoint, newest first. Back to the operation

Changed in 1 of the 4 revisions of this API.35338

Aug 12, 202687d29dc7b4fe35338

What changed

Aug 12, 202687d29dc7b4fe35338See the full diff
- ▲
  request body became required
  request-body-became-required
- ▲
  for the path request parameter id, the minLength was increased from 0 to 1
  request-parameter-min-length-increased
- ▲
  for the header request parameter x-checkly-account, the type/format was changed from string/ to string/uuid
  request-parameter-type-changed
- ▲
  for the path request parameter id, the type/format was changed from string/ to string/uuid
  request-parameter-type-changed
- ▲
  removed the enum value DELETE of the request property alertChannels/webhook/items/method
  request-property-enum-value-removed
- ▲
  removed the enum value GET of the request property alertChannels/webhook/items/method
  request-property-enum-value-removed
- ▲
  removed the enum value HEAD of the request property alertChannels/webhook/items/method
  request-property-enum-value-removed
- ▲
  removed the enum value PATCH of the request property alertChannels/webhook/items/method
  request-property-enum-value-removed
- ▲
  removed the enum value POST of the request property alertChannels/webhook/items/method
  request-property-enum-value-removed
- ▲
  removed the enum value PUT of the request property alertChannels/webhook/items/method
  request-property-enum-value-removed
- ▲
  the alertChannels/email/items/address request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/slack/items/url request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/sms/items/number request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/webhook/items/headers/items/key request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/webhook/items/method request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/webhook/items/name request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/webhook/items/queryParameters/items/key request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertChannels/webhook/items/url request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the id request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the name request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the privateLocations/items/ request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the request/query request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the tags/items/ request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the triggerIncident/serviceId request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ▲
  the alertSettings/parallelRunFailureThreshold/percentage request property type/format changed from number/ to integer/
  request-property-type-changed
- ▲
  the alertSettings/reminders/amount request property type/format changed from number/ to integer/
  request-property-type-changed
- ▲
  the alertSettings/reminders/interval request property type/format changed from number/ to integer/
  request-property-type-changed
- ▲
  the alertSettings/runBasedEscalation/failedRunThreshold request property type/format changed from number/ to integer/
  request-property-type-changed
- ▲
  the alertSettings/timeBasedEscalation/minutesFailingThreshold request property type/format changed from number/ to integer/
  request-property-type-changed
- ▲
  the triggerIncident/serviceId request property type/format changed from string/ to string/uuid
  request-property-type-changed
- ▲
  the response property alertChannels/email/items/address became optional for the status 200
  response-property-became-optional
- ▲
  the response property alertChannels/slack/items/url became optional for the status 200
  response-property-became-optional
- ▲
  the response property alertChannels/sms/items/number became optional for the status 200
  response-property-became-optional
- ▲
  the response property alertChannels/webhook/items/url became optional for the status 200
  response-property-became-optional
- ▲
  the created_at response's property type/format changed from string/date to string/date-time for status 200
  response-property-type-changed
- ●
  removed the optional property attributes from the response with the 401 status
  response-optional-property-removed
- ●
  removed the optional property attributes from the response with the 429 status
  response-optional-property-removed
- ●
  added the new undefined enum value to the runtimeId response property for the response status 200
  response-property-enum-value-added
- ○
  the request property alertChannels/email/items/address became optional
  request-property-became-optional
- ○
  the request property alertChannels/slack/items/url became optional
  request-property-became-optional
- ○
  the request property alertChannels/sms/items/number became optional
  request-property-became-optional
- ○
  the request property alertChannels/webhook/items/url became optional
  request-property-became-optional
- ○
  the assertions request property default value was added
  request-property-default-value-added
- ○
  the headers request property default value was added
  request-property-default-value-added
- ○
  the locations request property default value was added
  request-property-default-value-added
- ○
  the queryParameters request property default value was added
  request-property-default-value-added
- ○
  the tags request property default value was added
  request-property-default-value-added
- ○
  the activated request property default value true was removed
  request-property-default-value-removed
- ○
  the value request property default value was removed
  request-property-default-value-removed
- ○
  the value request property default value was removed
  request-property-default-value-removed
- ○
  added the new undefined enum value to the request property runtimeId
  request-property-enum-value-added
- ○
  the created_at request property type/format was generalized from string/date to string/date-time
  request-property-type-generalized
- ○
  added the non-success response with the status 400
  response-non-success-status-added
- ○
  the response property message became required for the status 401
  response-property-became-required
- ○
  the response property message became required for the status 403
  response-property-became-required
- ○
  the response property message became required for the status 429
  response-property-became-required
- ○
  the assertions response's property default value was added for the status 200
  response-property-default-value-added
- ○
  the headers response's property default value was added for the status 200
  response-property-default-value-added
- ○
  the locations response's property default value was added for the status 200
  response-property-default-value-added
- ○
  the queryParameters response's property default value was added for the status 200
  response-property-default-value-added
- ○
  the tags response's property default value was added for the status 200
  response-property-default-value-added
- ○
  the activated response's property default value true was removed for the status 200
  response-property-default-value-removed
- ○
  the value response's property default value was removed for the status 200
  response-property-default-value-removed
- ○
  the value response's property default value was removed for the status 200
  response-property-default-value-removed
- ○
  removed the 401.00 enum value from the statusCode response property for the response status 401
  response-property-enum-value-removed
- ○
  removed the 403.00 enum value from the statusCode response property for the response status 403
  response-property-enum-value-removed
- ○
  removed the 429.00 enum value from the statusCode response property for the response status 429
  response-property-enum-value-removed
- ○
  removed the DELETE enum value from the alertChannels/webhook/items/method response property for the response status 200
  response-property-enum-value-removed
- ○
  removed the Forbidden enum value from the error response property for the response status 403
  response-property-enum-value-removed
- ○
  removed the GET enum value from the alertChannels/webhook/items/method response property for the response status 200
  response-property-enum-value-removed
- ○
  removed the HEAD enum value from the alertChannels/webhook/items/method response property for the response status 200
  response-property-enum-value-removed
- ○
  removed the PATCH enum value from the alertChannels/webhook/items/method response property for the response status 200
  response-property-enum-value-removed
- ○
  removed the POST enum value from the alertChannels/webhook/items/method response property for the response status 200
  response-property-enum-value-removed
- ○
  removed the PUT enum value from the alertChannels/webhook/items/method response property for the response status 200
  response-property-enum-value-removed
- ○
  removed the Too Many Requests enum value from the error response property for the response status 429
  response-property-enum-value-removed
- ○
  removed the Unauthorized enum value from the error response property for the response status 401
  response-property-enum-value-removed
This revision also has 566 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog