Go back to MeetingBaas storage
Go back to MeetingBaas-managed storage.
From the next bot onwards, artifacts are stored by MeetingBaas again.
Nothing is deleted. Artifacts already in your buckets stay where they are and stay accessible through the API and signed URLs — bots recorded while the configuration was active keep resolving to it. Your credentials are retained for exactly that purpose. Removing our access to those buckets on your side will make those older artifacts unreadable to us.
Returns 404 if you have no configuration.
Authorization
ApiKeyAuth x-meeting-baas-api-key<token>
Your Meeting BaaS API key. Get one from your account settings.
In: header
Response Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://api.meetingbaas.com/v2/storage-config"{
"data": {
"enabled": true,
"message": "string",
"storage_config_id": "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
}