Changes to Login with JSON

Changed in 2 of the 5 revisions of this API.●4○9

1. Aug 8, 2025696ee83009f6○1
2. Aug 6, 202582f6f0eba091●4○8

What changed

• Aug 8, 2025696ee83009f6○1See the full diff
  • ○

    api operation id ApiLoginLoginRoleJson removed and replaced with 03_login_json

    api-operation-id-removed

• Aug 6, 202582f6f0eba091●4○8See the full diff
  • ●

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

    response-optional-property-removed

  • ●

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

    response-optional-property-removed

  • ●

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

    response-optional-property-removed

  • ●

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

    response-optional-property-removed

  • ○

    api operation id ApiLoginLoginRoleJson was added

    api-operation-id-added

  • ○

    api tag Authorization added

    api-tag-added

  • ○

    api tag Authentication removed

    api-tag-removed

  • ○

    added the new optional request property redirect

    new-optional-request-property

  • ○

    removed the non-success response with the status 401

    response-non-success-status-removed

  • ○

    added the optional property extra to the response with the 400 status

    response-optional-property-added

  • ○

    added the required property detail to the response with the 400 status

    response-required-property-added

  • ○

    added the required property status_code to the response with the 400 status

    response-required-property-added

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