Check that MeetingBaas can still use your buckets

Re-run the access check against your current configuration and record the result.

Writes, reads back and deletes a marker object in each bucket, exactly as the check that runs when a configuration is set. Use it after rotating a key or changing a bucket policy: credentials that quietly stopped working would otherwise first surface as a failed upload at the end of a real meeting.

Returns 200 with ok: true when the storage is healthy, or 200 with ok: false and the reason when it is not — the request succeeded either way, it is the storage that is unhealthy. Returns 404 if you have no configuration.

curl -X POST "https://api.meetingbaas.com/v2/storage-config/test"

{
  "data": {
    "error": "string",
    "ok": true
  },
  "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
}