Changes to List Clients

Changed in 17 of the 66 revisions of this API.▲45●6○58

1. Aug 12, 2026e59754bccd6e●1
2. Aug 10, 20267671374e96b6○4
3. Jul 29, 20266ba85920fb53▲8○10
4. Jul 23, 202602198b453e51○1
5. Jul 23, 2026367a21c392bc●1
6. Jul 21, 202625477a7cf18a○1
7. Jul 21, 202637505efd2701●1
8. Jul 21, 2026b7d6f0054ef2○1
9. Apr 16, 2026a5318c3cf1e3○1
10. Apr 3, 2026f87a90d5a2d0▲1○1
11. Apr 1, 202640bf219eced6▲13○5
12. Apr 1, 20266aaeba6ecdc5▲5○13
13. Apr 1, 2026674e0a229e8a▲13○5
14. Mar 25, 20268f87a9ea95d5●1○1
15. Mar 9, 20267101b25c7d6e●1○1
16. Mar 6, 2026b8632174e5a0●1
17. Jan 12, 2026a426ff0abf8f▲5○14

What changed

• Aug 12, 2026e59754bccd6e●1See the full diff
  • ●

    removed the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary from the response with the 200 status

    response-optional-property-removed

  This revision also has 16 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 10, 20267671374e96b6○4See the full diff
  • ○

    added model.client-support-bundle to the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current response property allOf list for the response status 200

    response-property-all-of-added

  • ○

    added model.client-support-bundle to the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished response property allOf list for the response status 200

    response-property-all-of-added

  • ○

    removed model.client-management-operation from the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    removed model.client-management-operation from the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished response property allOf list for the response status 200

    response-property-all-of-removed

• Jul 29, 20266ba85920fb53▲8○10See the full diff
  • ▲

    the response property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id response's property type/format changed from / to string/uuid for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id response's property type/format changed from / to string/uuid for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id response's property type/format changed from / to string/uuid for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id response's property type/format changed from / to string/uuid for status 200

    response-property-type-changed

  • ○

    added the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/updated_at to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/updated_at to the response with the 200 status

    response-optional-property-added

  • ○

    the response optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id became not read-only for the status 200

    response-optional-property-became-not-read-only

  • ○

    the response optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id became not read-only for the status 200

    response-optional-property-became-not-read-only

  • ○

    the response optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id became not read-only for the status 200

    response-optional-property-became-not-read-only

  • ○

    the response optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id became not read-only for the status 200

    response-optional-property-became-not-read-only

  • ○

    removed null.uuid from the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    removed null.uuid from the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/current/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    removed null.uuid from the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/artifact_id response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    removed null.uuid from the allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary/last_finished/allOf[model.client-management-operation]/allOf[subschema #2]/requested_by_user_id response property allOf list for the response status 200

    response-property-all-of-removed

• Jul 23, 202602198b453e51○1See the full diff
  • ○

    added the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary to the response with the 200 status

    response-optional-property-added

• Jul 23, 2026367a21c392bc●1See the full diff
  • ●

    removed the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary from the response with the 200 status

    response-optional-property-removed

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 21, 202625477a7cf18a○1See the full diff
  • ○

    added the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary to the response with the 200 status

    response-optional-property-added

• Jul 21, 202637505efd2701●1See the full diff
  • ●

    removed the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary from the response with the 200 status

    response-optional-property-removed

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 21, 2026b7d6f0054ef2○1See the full diff
  • ○

    added the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/support_bundle_summary to the response with the 200 status

    response-optional-property-added

• Apr 16, 2026a5318c3cf1e3○1See the full diff
  • ○

    added the optional property allOf[subschema #2]/data/items/allOf[subschema #2]/token/allOf[subschema #3]/created_by to the response with the 200 status

    response-optional-property-added

• Apr 3, 2026f87a90d5a2d0▲1○1See the full diff
  • ▲

    added the pattern ^((eq|neq):)?[0-9a-fA-F]{8}-([0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}$ to the query request parameter id

    request-parameter-pattern-added

  • ○

    for the query request parameter id, the type/format was generalized from string/uuid to string/

    request-parameter-type-generalized

• Apr 1, 202640bf219eced6▲13○5See the full diff
  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter completed_job_count

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter current_job_id

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter created_at

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter deleted_at

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter updated_at

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter configured_user

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter domain_controller

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter hostname

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter ip_address

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter last_checkin

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter name

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter user_sid

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter version

    request-parameter-pattern-added

  • ○

    for the query request parameter completed_job_count, the type/format was generalized from integer/ to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter created_at, the type/format was generalized from string/date-time to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter current_job_id, the type/format was generalized from integer/ to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter deleted_at, the type/format was generalized from string/date-time to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter updated_at, the type/format was generalized from string/date-time to string/

    request-parameter-type-generalized

• Apr 1, 20266aaeba6ecdc5▲5○13See the full diff
  • ▲

    for the query request parameter completed_job_count, the type/format was changed from string/ to integer/

    request-parameter-type-changed

  • ▲

    for the query request parameter created_at, the type/format was changed from string/ to string/date-time

    request-parameter-type-changed

  • ▲

    for the query request parameter current_job_id, the type/format was changed from string/ to integer/

    request-parameter-type-changed

  • ▲

    for the query request parameter deleted_at, the type/format was changed from string/ to string/date-time

    request-parameter-type-changed

  • ▲

    for the query request parameter updated_at, the type/format was changed from string/ to string/date-time

    request-parameter-type-changed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter completed_job_count

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter current_job_id

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter created_at

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter deleted_at

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter updated_at

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter configured_user

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter domain_controller

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter hostname

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter ip_address

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter last_checkin

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter name

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter user_sid

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter version

    request-parameter-pattern-removed

• Apr 1, 2026674e0a229e8a▲13○5See the full diff
  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter completed_job_count

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter current_job_id

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter created_at

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter deleted_at

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter updated_at

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter configured_user

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter domain_controller

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter hostname

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter ip_address

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter last_checkin

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter name

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter user_sid

    request-parameter-pattern-added

  • ▲

    added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter version

    request-parameter-pattern-added

  • ○

    for the query request parameter completed_job_count, the type/format was generalized from integer/ to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter created_at, the type/format was generalized from string/date-time to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter current_job_id, the type/format was generalized from integer/ to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter deleted_at, the type/format was generalized from string/date-time to string/

    request-parameter-type-generalized

  • ○

    for the query request parameter updated_at, the type/format was generalized from string/date-time to string/

    request-parameter-type-generalized

• Mar 25, 20268f87a9ea95d5●1○1See the full diff
  • ●

    added the new openhound enum value to the allOf[subschema #2]/data/items/allOf[subschema #2]/type response property for the response status 200

    response-property-enum-value-added

  • ○

    removed the ogcollector enum value from the allOf[subschema #2]/data/items/allOf[subschema #2]/type response property for the response status 200

    response-property-enum-value-removed

• Mar 9, 20267101b25c7d6e●1○1See the full diff
  • ●

    added the new ogcollector enum value to the allOf[subschema #2]/data/items/allOf[subschema #2]/type response property for the response status 200

    response-property-enum-value-added

  • ○

    removed the opengraph_collector_platform enum value from the allOf[subschema #2]/data/items/allOf[subschema #2]/type response property for the response status 200

    response-property-enum-value-removed

• Mar 6, 2026b8632174e5a0●1See the full diff
  • ●

    added the new opengraph_collector_platform enum value to the allOf[subschema #2]/data/items/allOf[subschema #2]/type response property for the response status 200

    response-property-enum-value-added

• Jan 12, 2026a426ff0abf8f▲5○14See the full diff
  • ▲

    for the query request parameter completed_job_count, the type/format was changed from string/ to integer/

    request-parameter-type-changed

  • ▲

    for the query request parameter created_at, the type/format was changed from string/ to string/date-time

    request-parameter-type-changed

  • ▲

    for the query request parameter current_job_id, the type/format was changed from string/ to integer/

    request-parameter-type-changed

  • ▲

    for the query request parameter deleted_at, the type/format was changed from string/ to string/date-time

    request-parameter-type-changed

  • ▲

    for the query request parameter updated_at, the type/format was changed from string/ to string/date-time

    request-parameter-type-changed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter completed_job_count

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter current_job_id

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter created_at

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter deleted_at

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter updated_at

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter configured_user

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter domain_controller

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter hostname

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter ip_address

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter last_checkin

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter name

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter user_sid

    request-parameter-pattern-removed

  • ○

    removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter version

    request-parameter-pattern-removed

  • ○

    removed the openhound enum value from the allOf[subschema #2]/data/items/allOf[subschema #2]/type response property for the response status 200

    response-property-enum-value-removed

  This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog