# Attaching Custom Metadata to the Connect Webview Adding Custom Metadata to a Connect Webview enables you to store custom information, like customer details or internal IDs from your application. The `custom_metadata` is then transferred to any connected accounts connected through the connect webview, making it easy to find and filter these resources in your Seam workspace. {% hint style="info" %} You can also use unique resource keys as an easy way to link your resources to Seam resources. For details, see [Mapping Your Resources to Seam Resources](/latest/core-concepts/mapping-your-resources-to-seam-resources.md). {% endhint %} The `custom_metadata` property supports up to 50 JSON key:value pairs. When an account is successfully connected through a Connect Webview, Seam creates a connected account and copies the `custom_metadata` to it. {% hint style="info" %} If the `custom_metadata` property is left blank, Seam stores an empty set (`{}`) on both the Connect Webview and connected account resource. {% endhint %} To add `custom_metadata` to a Connect Webview: 1. Execute [`/connect_webviews/create`](https://docs.seam.co/latest/api/connect_webviews/create) and specify the internal ID as a key:value pair in the `custom_metadata`.\ For example: {% tabs %} {% tab title="JavaScript" %} **Request:** ```javascript await seam.connectWebviews.create({ provider_category: "stable", custom_metadata: { "your_app_user_id": "xxxx" // Insert your custom data here. } }) ``` **Response:** ```json { url: 'https://connect.getseam.com/connect_webviews/view?connect_webview_id=3937fa0b-ab09-4a00-9f10-69864750ed07&auth_token=PVHmtzULRFEQDny776KDsegSQ5t2SsZHR', status: 'pending', workspace_id: '398d80b7-3f96-47c2-b85a-6f8ba21d07be', custom_metadata: { id: 'internalId1' }, ... } ``` {% endtab %} {% tab title="cURL" %} **Request:** ```bash curl -X 'POST' \ 'https://connect.getseam.com/connect_webviews/create' \ -H 'accept: application/json' \ -H 'Authorization: Bearer ${API_KEY}' \ -H 'Content-Type: application/json' \ -d '{ "provider_category": "stable", "custom_metadata": { "your_app_user_id": "xxxx" } }' ``` **Response:** ```json { "connect_webview": { "url": "https://connect.getseam.com/connect_webviews/view?connect_webview_id=3c3f4c15-e7db-47c6-bc5a-1bf206ff269c&auth_token=LrpMC4MVHAY8YJRcNFeX1nQcb7tGNwpot", "status": "pending", "workspace_id": "398d80b7-3f96-47c2-b85a-6f8ba21d07be", "custom_metadata": { "id": "internal_id_1" }, ... }, "ok": true } ``` {% endtab %} {% tab title="Python" %} **Request:** ```python seam.connect_webviews.create( provider_category = "stable", custom_metadata = { "your_app_user_id": "xxxx" # Insert your custom data here. } ) ``` **Response:** ``` ConnectWebview( workspace_id='398d80b7-3f96-47c2-b85a-6f8ba21d07be', connect_webview_id='49e050d9-cb4c-4600-b24d-cdf9dd2f92b7', status='pending', url='https://connect.getseam.com/connect_webviews/view?connect_webview_id=49e050d9-cb4c-4600-b24d-cdf9dd2f92b7&auth_token=C1r8ff3GLSr2L1ifEaCopAgrq2Faht2Dh', custom_metadata={'id': 'internal_id_1'}, ... ) ``` {% endtab %} {% tab title="Ruby" %} **Request:** ```ruby client.connect_webviews.create( provider_category: "stable", custom_metadata: { "your_app_user_id": "xxxx" # Insert your custom data here. } ) ``` **Response:** ``` "internal_id_1"} ... > ``` {% endtab %} {% tab title="C#" %} **Request:** ```csharp var customMetadata = new Dictionary() { {"id", "internal-user-id"} }; seam.ConnectWebviews.Create( providerCategory: Seam.Api.ConnectWebviews.CreateRequest.ProviderCategoryEnum.Stable, customMetadata: customMetadata ); ``` **Response:** ``` { "connect_webview_id": "3874d8b4-4bb5-470a-9fc7-a54931a4b933", "url": "https://connect.getseam.com/connect_webviews/view?connect_webview_id=3874d8b4-4bb5-470a-9fc7-a54931a4b933&auth_token=F9t4SkQ6R8mZjJEBV5K4dwoVdkR6VtjdJ", "workspace_id": "398d80b7-3f96-47c2-b85a-6f8ba21d07be", "custom_metadata": { "id": "user1" }, ... } ``` {% endtab %} {% endtabs %} 2. Your app presents the Connect Webview to your user. 3. The user completes the Connect Webview. 4. Seam creates a connected account containing the user's device account information.\ This connected account includes a `custom_metadata` property that automatically contains the information that you set in the `custom_metadata` property for the Connect Webview. 5. To retrieve the ID of the connected account associated with the completed Connect Webview, [get the `connect_webview`](https://docs.seam.co/latest/api/connect_webviews/get) and check the `connected_account_id` property. 6. To retrieve the connected account, [get the `connected_account`](https://docs.seam.co/latest/api/connected_accounts/get) with the ID that you identified in the previous step. 7. Within the returned `connected_account`, view the `custom_metadata`. {% hint style="info" %} If a Connect Webview was used to connect an existing connected account (for example, to reconnect a disconnected account), Seam will replace any existing `custom metadata` in the `connected_account` object with the new payload. {% endhint %} ## Next Steps Once you have attached custom metadata to Connect Webviews, you can [filter your Connect Webviews](/latest/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata.md) by this custom metadata. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.seam.co/latest/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.