e57ab8cb0c
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Alexandre Girard <alexandre@airbyte.io>
30 lines
1.6 KiB
Markdown
30 lines
1.6 KiB
Markdown
# Managing Airbyte Embedded
|
|
|
|
## Customer Workspaces
|
|
|
|
Airbyte Embedded is built upon the Airbyte Platform. As the owner of your embedded instance, you access Airbyte via the standard sign-in. Each customer who configures a source via the Embedded Widget is automatically assigned a workspace. Within this workspace, data pipelines are created between the source and staging store, which you configured in the pre-requisite section of this guide. In this example, the staging store is S3.
|
|
|
|
|
|
|
|
## Enabling Connectors within the Widget
|
|
|
|
Source connectors can be configured to appear in the Embedded widget by creating a configuration template [via the source_template endpoint](https://api.airbyte.ai/api/v1/docs#tag/Template-Sources/operation/create_integrations_templates_sources).
|
|
|
|
The following example demonstrates how to use the API to create a new configuration template for the Faker connector, with a required “*count*” field. To obtain the `source_connector_definition_id`, you can access this via the [Airbyte Connector Registry](https://connectors.airbyte.com/files/generated_reports/connector_registry_report.html).
|
|
|
|
```bash
|
|
curl --request POST \
|
|
--url https://api.airbyte.ai/api/v1/integrations/templates/sources \
|
|
--header 'Content-Type: application/json' \
|
|
--header 'Authorization: Bearer <bearer id>' \
|
|
--data '{
|
|
"organization_id": "<organization id>",
|
|
"actor_definition_id": "<actor id>",
|
|
"partial_default_config": {}
|
|
}'
|
|
```
|
|
|
|
:::note
|
|
This endpoint is only available to Embedded customers.
|
|
:::
|