Submit interaction

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://openapi.logto.io/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "Logto API references MCP server": {
    "url": "https://openapi.logto.io/mcp"
  }
}
Close
POST /api/experience/submit

Submit the current interaction.
- Submit the verified user identity to the OIDC provider for further authentication (SignIn and Register).
- Update the user's profile data if any (SignIn and Register).
- Reset the password and clear all the interaction records (ForgotPassword).
- Complete a step-up interaction: the interaction must have reached the authentication context class the authorization request selected, and only the methods it established are written to the account, with no sign-in side effect.

Responses

  • 200 application/json

    The interaction has been submitted. A sign-in with requested acr_values that cannot reach any requested class, even through first-factor establishment or MFA enrollment, finishes with the OIDC error unmet_authentication_requirements. Follow redirectTo to return the error to the client; no sign-in side effect runs.

    Hide response attribute Show response attribute object
    • redirectTo string Required
  • 400

    Bad Request

  • 403

    Multi-Factor Authentication (MFA) is enabled for the user but has not been verified (SignIn and Register).
    - A sign-in with requested acr_values still lacks a Logto-verifiable first factor (session.step_up.require_verification); the response data carries the selected authentication context class, the available methods, and the masked identifiers.
    - The achieved authentication context does not satisfy the requested authentication context class (session.step_up.acr_not_satisfied); no interaction result is written.

  • 404

    The user has not been identified.

  • 422

    The user profile cannot be processed because it is invalid, conflicts with existing data, is already in use, or lacks required fields.
    - A sign-in with requested acr_values has no eligible method but holds a fresh subject proof (user.missing_profile); data.isEstablishment is true and data.missingProfile lists alternative first-factor methods the tenant allows the user to establish. Establishing any one method fulfills this requirement; tenant-mandated profile fields are checked separately on the next submission. When data.isEstablishment is absent, every entry in data.missingProfile is required.
    - Requested MFA requires enrollment (user.missing_mfa); data.availableFactors lists the factors to bind.

POST /api/experience/submit 
curl \
 --request POST 'https://[tenant_id].logto.app/api/experience/submit'
Response examples (200) 
{
  "redirectTo": "string"
}