You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`AIRBYTE_BASE_URL`: where your Airbyte instance is deployed
54
-
`CUSTOMER_WORKSPACE_ID`: the workspace you have associated with this customer
55
-
`EMBEDDING_ORIGIN` here refers to where you are adding this widget to. It will be used to generate an `allowedOrigin` parameter for the webapp to open communications with the widget.
79
+
-`AIRBYTE_BASE_URL`: where your Airbyte instance is deployed
80
+
-`CUSTOMER_WORKSPACE_ID`: the workspace you have associated with this customer
81
+
-`EMBEDDING_ORIGIN`: the origin where you're embedding the widget (used for CORS validation)
56
82
57
-
You can also, optionally, send an `externalUserId` in your request and we will attach it to the jwt encoded within the Airbyte Embedded token for provenance purposes.
83
+
You can also, optionally, send an `externalUserId` in your request and we will attach it to the JWT encoded within the Airbyte Embedded token for provenance.
58
84
59
-
Embedded tokens are short-lived (15-minutes) and only allow an end user to create and edit Airbyte source configurations within the workspace you have created for them.
85
+
Embedded tokens are short-lived (15 minutes) and only allow the user to create/edit configurations within the scoped workspace.
86
+
87
+
---
60
88
61
89
### Event Callbacks
62
90
63
-
The widget also accepts an `onEvent`function as an argument. This function, if provided, will be executed when a user completes the integration setup or update flow. These events have the following format:
91
+
You can pass an `onEvent`callback to receive messages when the user completes actions in the widget:
data: PartialUserConfigRead;// an object containing all data related to the user's configuration, including an actorId identifying the source created/updated
0 commit comments