Configure GCS, S3, and Azure connectors

Choose connector scopes first

A connector can support:

• import
• export
• both

If the connector should only receive exports, do not give it import scope.

Create a GCS connector

GCS connector creation uses multipart form data because the public surface accepts a service account JSON file.

curl -X POST https://playground-api-stg-udk7d32fva-uc.a.run.app/api/v2/connectors/gcs \
  -H "Authorization: Bearer <token-or-api-key>" \
  -F "name=Broadcast storage" \
  -F "bucket=archive-bucket" \
  -F "gcp_project_id=media-project-123" \
  -F "scopes=import" \
  -F "credentials_file=@service-account.json"

Create S3 or Azure connectors

S3 and Azure connector creation uses JSON payloads with provider-specific credentials and optional export_base_path.

Test and browse the connector

After creation:

1. Call the test endpoint to validate credentials and access.
2. Browse the connector with a prefix and pattern before you start an import job.

connector = client.connectors.create_s3(
    name="Archive S3",
    bucket="media-archive",
    region="us-east-1",
    aws_access_key_id="AKIA...",
    aws_secret_access_key="...",
    scopes=["import", "export"],
    export_base_path="exports/team-a",
)

client.connectors.test(connector.connector_id)
files = client.connectors.browse(connector.connector_id, prefix="incoming/", pattern="*.mp4")

Import mode

Connectors expose import_mode such as:

• all
• new_only

Use new_only when the connector should behave as a dedupe-oriented ingestion source across repeated workflows.