Changes to Checks whether a user with the given email exists in the system

Changed in 1 of the 3 revisions of this API.▲1●4○5

1. Jul 30, 202682ed767ffb65▲1●4○5

What changed

• Jul 30, 202682ed767ffb65▲1●4○5See the full diff
  • ▲

    the status response's property type changed from integer to string, and format from int32 to no format for status 200

    response-property-type-changed

  • ●

    removed the optional property error from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property message from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property path from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property timestamp from the response with the 200 status

    response-optional-property-removed

  • ○

    added the non-success response with the status 400

    response-non-success-status-added

  • ○

    added the non-success response with the status 403

    response-non-success-status-added

  • ○

    added the optional property body to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property header to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property id to the response with the 200 status

    response-optional-property-added

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

Of the 3 revisions, 1 has no diff computed.