Set your storage configuration

Point MeetingBaas at object storage you own.

From the next bot onwards, every artifact we produce for you — recording, audio chunks, raw and diarized transcripts, screenshots and bot logs — is written to your buckets with your credentials. Nothing lands in MeetingBaas storage.

Verified before it is accepted. The ingest key writes a small marker object into each bucket and the service key reads, writes and deletes it — each operation exercised with the credential that will really perform it, which also catches two key pairs that point at different buckets. Ingest upload receives recordings; service upload writes transcripts and reconciled artifacts; read serves artifacts; and delete enforces data retention. If any step fails the request returns 400 with the reason and your existing configuration is left untouched.

Settings: endpoint, region and force_path_style are the same knobs as a self-hosted deployment. Any S3-compatible provider works; enable force_path_style for MinIO, Ceph and most self-hosted gateways. The three buckets may all be the same bucket — keys are prefixed with the bot id regardless.

Two credentials. The ingest key is write-only (s3:PutObject, s3:PutObjectTagging, s3:AbortMultipartUpload) and is the only one that leaves our infrastructure — it is handed to the recording bot, which runs a browser inside your meeting. Scoped this way, a compromised bot can add objects and nothing else. The service key (s3:GetObject, s3:ListBucket, s3:PutObject, s3:DeleteObject) stays in our API and does everything else: serving your recordings back, writing transcripts, and deleting artifacts when your retention period expires.

Keep the buckets private — artifacts are served through short-lived signed URLs — but they must be reachable from the public internet, because transcription providers fetch audio directly from a signed URL.

Data residency. By default (allow_transient_spill: false) nothing you record ever rests on MeetingBaas storage: if an upload to your bucket fails and retries are exhausted, the artifact is reported as failed and lost rather than parked on our infrastructure. Set it to true if you would rather we hold a copy until the upload can be retried.

Replacing a configuration is safe. Calling this again supersedes the previous configuration for new bots only. Bots recorded earlier keep resolving to the storage they were written to, so their artifacts stay readable and deletable — nothing is migrated or re-pointed.

Returns 200 with the stored configuration.

curl -X PUT "https://api.meetingbaas.com/v2/storage-config" \  -H "Content-Type: application/json" \  -d '{    "artifacts_bucket": "acme-meeting-artifacts",    "audio_chunks_bucket": "acme-meeting-audio-chunks",    "endpoint": "https://s3.eu-west-3.amazonaws.com",    "ingest_access_key_id": "AKIAIOSFODNN7EXAMPLE",    "ingest_secret_access_key": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY",    "logs_bucket": "acme-meeting-logs",    "region": "eu-west-3",    "service_access_key_id": "AKIAI44QH8DHBEXAMPLE",    "service_secret_access_key": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"  }'

{
  "data": {
    "allow_transient_spill": true,
    "artifacts_bucket": "string",
    "audio_chunks_bucket": "string",
    "created_at": "string",
    "enabled": true,
    "endpoint": "string",
    "force_path_style": true,
    "ingest_access_key_id": "string",
    "last_error_at": "string",
    "last_error_message": "string",
    "last_verified_at": "string",
    "logs_bucket": "string",
    "region": "string",
    "service_access_key_id": "string",
    "storage_config_id": "string",
    "updated_at": "string"
  },
  "success": true
}

{
  "code": "string",
  "error": "string",
  "message": "string",
  "statusCode": 9007199254740991,
  "success": false
}

{
  "code": "string",
  "details": "string",
  "error": "string",
  "message": "string",
  "retryAfter": 9007199254740991,
  "statusCode": 9007199254740991,
  "success": false
}

{
  "code": "string",
  "details": "string",
  "error": "string",
  "message": "string",
  "statusCode": 9007199254740991,
  "success": false
}