Retrieve items by multiple ids

Changes

Changed in 1 of the 7 revisions of this API.▲56

• Jul 27, 20264b624af2cb6e▲56See the full diff
  • ▲

    the response property items/created became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/description became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/lastModified became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/mode became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/projectId became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/tags became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userId became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/bandwidth became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/browser became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/dns became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/jtl became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/properties became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/properties/map became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting/listeners became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting/queueSize became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/setUp/scope became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/tearDown/scope became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/thinkTime became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting/listeners became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting/queueSize became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/setUp/scope became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/tearDown/scope became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/thinkTime became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/bandwidth became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting/listeners became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting/queueSize became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/setUp/scope became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/tearDown/scope became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/thinkTime became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/memory became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property items/userProfiles/items/name became nullable for the status 200

    response-property-became-nullable

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/bandwidth response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/browser response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/dns response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/jtl response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/properties response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/JmeterUserProfileEngine]/allOf[subschema #2]/settings/thinkTime response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/PlaywrightUserProfileEngine]/allOf[subschema #2]/settings/thinkTime response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/bandwidth response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/externalLiveReporting response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/engine/oneOf[#/components/schemas/SeleniumUserProfileEngine]/allOf[subschema #2]/settings/thinkTime response's property type changed from object to null for status 200

    response-property-type-changed

  • ▲

    the items/userProfiles/items/memory response's property type changed from object to null for status 200

    response-property-type-changed

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