{
  "opencollection": "1.0.0",
  "info": {
    "name": "Stytch B2B Authentication Application B2B Passwords API",
    "version": "2.0.0"
  },
  "items": [
    {
      "info": {
        "name": "B2B Passwords",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Resetstart",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.stytch.com/v1/b2b/passwords/email/reset/start",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Initiates a password reset for the email address provided. This will trigger an email to be sent to the address, containing a magic link that will allow them to set a new password and authenticate.\n\nThis endpoint adapts to your Project's password strength configuration.\nIf you're using [zxcvbn](https://stytch.com/docs/guides/passwords/strength-policy), the default, your passwords are considered valid\nif the strength score is >= 3. If you're using [LUDS](https://stytch.com/docs/guides/passwords/s"
        },
        {
          "info": {
            "name": "Reset",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.stytch.com/v1/b2b/passwords/email/reset",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Reset the Member's password and authenticate them. This endpoint checks that the password reset token is valid, hasn’t expired, or already been used.\n\nThe provided password needs to meet our password strength requirements, which can be checked in advance with the password strength endpoint. If the token and password are accepted, the password is securely stored for future authentication and the user is authenticated.\n\nIf the Member is required to complete MFA to log in to the Organization, the r"
        },
        {
          "info": {
            "name": "Requirereset",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.stytch.com/v1/b2b/passwords/email/require_reset",
            "headers": [
              {
                "name": "X-Stytch-Member-Session",
                "value": ""
              },
              {
                "name": "X-Stytch-Member-SessionJWT",
                "value": ""
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Require a password be reset by the associated email address. This endpoint is only functional for cross-org password use cases.\n\nIf there are is only one active Member using the associated email address in the Project, the password will be deleted."
        },
        {
          "info": {
            "name": "Reset",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.stytch.com/v1/b2b/passwords/session/reset",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Reset the Member's password using their existing session. The endpoint will error if the session does not contain an authentication factor that has been issued within the last 5 minutes. Either `session_token` or `session_jwt` should be provided.\n\nNote that a successful password reset via an existing session will revoke all active sessions for the `member_id`, except for the one used during the reset flow."
        },
        {
          "info": {
            "name": "Reset",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.stytch.com/v1/b2b/passwords/existing_password/reset",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Reset the member's password using their existing password.\n\nThis endpoint adapts to your Project's password strength configuration.\nIf you're using [zxcvbn](https://stytch.com/docs/guides/passwords/strength-policy), the default, your passwords are considered valid\nif the strength score is >= 3. If you're using [LUDS](https://stytch.com/docs/guides/passwords/strength-policy), your passwords are\nconsidered valid if they meet the requirements that you've set with Stytch.\nYou may update your passwor"
        },
        {
          "info": {
            "name": "Authenticate",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.stytch.com/v1/b2b/passwords/discovery/authenticate",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Authenticate an email/password combination in the discovery flow. This authenticate flow is only valid for cross-org passwords use cases, and is not tied to a specific organization.\n\nIf you have breach detection during authentication enabled in your [password strength policy](https://stytch.com/docs/b2b/guides/passwords/strength-policy) and the member's credentials have appeared in the HaveIBeenPwned dataset, this endpoint will return a `member_reset_password` error even if the member enters a c"
        }
      ]
    }
  ],
  "bundled": true
}