@seamapi/http - v1.76.0
    Preparing search index...

    Class SeamHttpConnectedAccounts

    Index

    Constructors

    Properties

    client: AxiosInstance
    defaults: Required<SeamHttpRequestOptions>
    ltsVersion: "1.0.0" = seamApiLtsVersion
    ltsVersion: string = seamApiLtsVersion

    Methods

    • Parameters

      • Optionalparameters: {
            custom_metadata_has?: { [x: string]: string | boolean };
            customer_key?: string;
            limit?: number;
            page_cursor?: null | string;
            search?: string;
            user_identifier_key?: string;
        }
        • Optionalcustom_metadata_has?: { [x: string]: string | boolean }

          Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with custom_metadata that contains all of the provided key:value pairs.

        • Optionalcustomer_key?: string

          Customer key by which you want to filter connected accounts.

        • Optionallimit?: number

          Maximum number of records to return per page.

        • Optionalpage_cursor?: null | string

          Identifies the specific page of results to return, obtained from the previous page's next_page_cursor.

        • Optionalsearch?: string

          String for which to search. Filters returned connected accounts to include all records that satisfy a partial match using connected_account_id, account_type, customer_key, custom_metadata, user_identifier.username, user_identifier.email or user_identifier.phone.

        • Optionaluser_identifier_key?: string

          Your user ID for the user by which you want to filter connected accounts.

      • options: ConnectedAccountsListOptions = {}

      Returns ConnectedAccountsListRequest

    • Parameters

      • Optionalparameters: {
            accepted_capabilities?: (
                "lock"
                | "thermostat"
                | "noise_sensor"
                | "access_control"
            )[];
            automatically_manage_new_devices?: boolean;
            connected_account_id: string;
            custom_metadata?: { [x: string]: null | string | boolean };
            customer_key?: string;
        }
        • Optionalaccepted_capabilities?: ("lock" | "thermostat" | "noise_sensor" | "access_control")[]

          List of accepted device capabilities that restrict the types of devices that can be connected through this connected account. Valid values are lock, thermostat, noise_sensor, and access_control.

        • Optionalautomatically_manage_new_devices?: boolean

          Indicates whether newly-added devices should appear as managed devices.

        • connected_account_id: string

          ID of the connected account that you want to update.

        • Optionalcustom_metadata?: { [x: string]: null | string | boolean }

          Custom metadata that you want to associate with the connected account. Entirely replaces the existing custom metadata object. If a new Connect Webview contains custom metadata and is used to reconnect a connected account, the custom metadata from the Connect Webview will entirely replace the entire custom metadata object on the connected account. Supports up to 50 JSON key:value pairs. Adding custom metadata to a connected account enables you to store custom information, like customer details or internal IDs from your application. Then, you can filter connected accounts by the desired metadata.

        • Optionalcustomer_key?: string

          The customer key to associate with this connected account. If provided, the connected account and all resources under the connected account will be moved to this customer. May only be provided if the connected account is not already associated with a customer.

      • options: ConnectedAccountsUpdateOptions = {}

      Returns ConnectedAccountsUpdateRequest

    • Parameters

      • clientSessionToken: string

      Returns Promise<void>