Properties
| Name | Type | Description |
|---|---|---|
| mfaInfoTitle | string | The title for the MFA information demanded from the user.This is the title displayed in the provider site.This field is applicable for MFA form types only. Endpoints:
|
| help | string | The help that can be displayed to the customer in the login form. Endpoints:
|
| forgetPasswordURL | string | The forget password URL of the provider site. Endpoints:
|
| formType | string | The type of the forms for which the user information is required. Endpoints:
|
| mfaInfoText | string | The text displayed in the provider site while requesting the user's MFA information. This field is applicable for MFA form types only. Endpoints:
|
| loginHelp | string | The help that can be displayed to the customer in the login form. Endpoints:
|
| mfaTimeout | integer | The amount of time before which the user is expected to provide MFA information. This field is applicable for MFA form types only. This would be an useful information that could be displayed to the us |
| id | integer | The identifier of the login form. Endpoints:
|
| row | array | This indicates one row in the form. The row will have one label. But it may have single or multiple fields. Endpoints:
|
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/LoginForm",
"title": "LoginForm",
"type": "object",
"properties": {
"mfaInfoTitle": {
"type": "string",
"description": "The title for the MFA information demanded from the user.This is the title displayed in the provider site.This field is applicable for MFA form types only. <br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li></ul>",
"readOnly": true
},
"help": {
"type": "string",
"description": "The help that can be displayed to the customer in the login form.<br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul>",
"readOnly": true
},
"forgetPasswordURL": {
"type": "string",
"description": "The forget password URL of the provider site.<br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul>"
},
"formType": {
"type": "string",
"description": "The type of the forms for which the user information is required.<br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul><b>Applicable Values</b><br>",
"enum": [
"login",
"questionAndAnswer",
"token",
"image"
]
},
"mfaInfoText": {
"type": "string",
"description": "The text displayed in the provider site while requesting the user's MFA information. This field is applicable for MFA form types only. <br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li></ul>",
"readOnly": true
},
"loginHelp": {
"type": "string",
"description": "The help that can be displayed to the customer in the login form.<br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul>",
"readOnly": true
},
"mfaTimeout": {
"type": "integer",
"description": "The amount of time before which the user is expected to provide MFA information. This field is applicable for MFA form types only. This would be an useful information that could be displayed to the users. <br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul>",
"format": "int64",
"readOnly": true
},
"id": {
"type": "integer",
"description": "The identifier of the login form.<br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul>",
"format": "int64"
},
"row": {
"type": "array",
"description": "This indicates one row in the form. The row will have one label. But it may have single or multiple fields.<br><br><b>Endpoints</b>:<ul><li>GET providerAccounts/{providerAccountId}</li><li>GET providers/{providerId}</li></ul>",
"items": {
"$ref": "#/components/schemas/Row"
}
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/envestnet-loginform"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.