> ## Documentation Index
> Fetch the complete documentation index at: https://docs.methodfi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Element Specific Events

export const ParamList = ({items = [], is_child = false}) => {
  return items.map(item => {
    const field_props = {
      id: Math.random().toString(),
      body: item.name,
      name: item.name,
      type: item.type,
      required: item.required
    };
    const enums = item.enums || [];
    const items = item.items || [];
    const has_items = items?.length > 0;
    const has_enums = enums?.length > 0;
    const should_default_open = item.defaultOpen || false;
    const render_child_item = () => {
      const child_props = {
        title: has_enums ? "Possible enum values" : "properties"
      };
      if (should_default_open) child_props.defaultOpen = true;
      const has_inline_enums = has_enums && enums.every(enum_item => typeof enum_item === 'string') && enums.map((enum_item, idx) => {
        const is_last = idx === enums.length - 1;
        const is_2nd_to_last = idx === enums.length - 2;
        return <>
            <code>{enum_item}</code>
            {is_last && ''}
            {is_2nd_to_last && ' or '}
            {!is_last && !is_2nd_to_last && ', '}
          </>;
      });
      const enum_list = has_enums && !has_inline_enums && <Accordion {...child_props}>
          {enums.map((enum_item, index) => <div key={`enum-${index}`}>
              <code>{enum_item.name}</code>
              <br />
              <p>{enum_item.description}</p>
            </div>)}
        </Accordion>;
      const item_list = has_items && <Expandable {...child_props}>
          <ParamList items={items || []} is_child />
        </Expandable>;
      return <>
          <p>
            {item.description}
            {has_inline_enums && [has_inline_enums.length > 1 ? ' One of ' : ' Must be ', ...has_inline_enums]}
          </p>

          {enum_list}
          {item_list}
        </>;
    };
    return is_child ? <ResponseField {...field_props}>{render_child_item()}</ResponseField> : <ParamField {...field_props}>{render_child_item()}</ParamField>;
  });
};

<Warning>
  Method Elements will no longer be supported or maintained beginning December
  31st, 2025. We recommend using [Method Opal](/opal/overview) for all new
  integrations. If you are currently using Elements, please reach out to your
  CSM to discuss your migration options.
</Warning>

## Connect

Connect will emit a `success` event when the user has successfully completed all required authentication and verification:

```bash theme={null}
methodelements://connect
  ?op=success
  &element_type=connect
  &entity_id=ent_WyDmJnQgaxVRH
  &accounts=["acc_PFUNazUbpUpfm","acc_gjWr4Cb8H7TLz"]
```

When parsed, will result in the following JSON

```json theme={null}
{
  "op": "success",
  "element_type": "connect",
  "entity_id": "ent_WyDmJnQgaxVRH",
  "accounts": ["acc_PFUNazUbpUpfm","acc_gjWr4Cb8H7TLz"]
}
```

This will list all of the accounts that were consented and connected to at least one of the products passed into the Element token creation (Note: Some accounts are ineligible for some products).

## Other Events

For more granular information about specific actions a user is taking, `auth` and `account_verification` will emit the following events.

### Auth

Auth will emit a variety of events that describe how the user is progressing through the authentication process. Most events are of the following form:

```bash theme={null}
AUTH_{STEP}_{ACTION}
```

STEP will reference a step during the auth process: `INTRO`, `NAME`, `PHONE`, `PHONE_VERIFY`, `DOB`, `ADDRESS`, `SSN4`, `SECQ`, and `CONSENT`.

ACTION will refer to the action the user took: `OPEN`, `CONTINUE`, `SUBMIT`, and `CLOSE`.

**Note**: Not all steps will have all actions, and that there are a few actions that do not follow this pattern

For example, if the user was prompted for the last 4 of their SSN, then submitted their info and was directed to the DOB page, you would see the following events:

```bash theme={null}
AUTH_SSN4_OPEN
AUTH_SSN4_CONTINUE
AUTH_DOB_OPEN
```

### Account Verification

Account Verification will emit a variety of events using a similar structure to auth:

```bash theme={null}
AVF_{STEP}_{ACTION}
```

STEP will reference a step during the account verification process: `ACCOUNT_LIST`, `LEARN_MORE`, and `ACCOUNT_VERIFY`.

ACTION will refer to the action the user took: `OPEN`, `CONTINUE`, `SUBMIT`, `SKIP`, and `CLOSE`.

For example, if the user was prompted to verify their credit card, then submitted their info and was directed to the success screen, you would see the following events:

```bash theme={null}
AVF_ACCOUNT_VERIFY_OPEN
AVF_ACCOUNT_VERIFY_SUBMIT
AVF_SUCCESS_OPEN
```