Changes to Register Flows

Changed in 2 of the 5 revisions of this API.▲1●1○10

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

What changed

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

    api operation id FlowRegisterRegisterFlow removed and replaced with 10_register_flow

    api-operation-id-removed

• Aug 6, 202582f6f0eba091▲1●1○9See the full diff
  • ▲

    removed the success response with the status 200

    response-success-status-removed

  • ●

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

    response-optional-property-removed

  • ○

    api operation id FlowRegisterRegisterFlow was added

    api-operation-id-added

  • ○

    api tag Flow Operations added

    api-tag-added

  • ○

    api tag Flow Management removed

    api-tag-removed

  • ○

    request property url list-of-types was widened by adding types string to media type application/json

    request-property-list-of-types-widened

  • ○

    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

  • ○

    added the success response with the status 201

    response-success-status-added

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