Skip to content

Storage API

7 confirmed endpoints — 3 respond with data, 4 require valid input.

Endpoints with Response Data

GET /ingest/api/v1/generatedMediaLocations

Get tenant generated media locations

✅ Live — responds with data

Sample Response:

[
  {
    "id": "mimir-stg-generated-media-1/",
    "bucketName": "mimir-stg-generated-media-1",
    "pathPrefix": "",
    "backup": false,
    "deleteEnabled": false,
    "autoCreateItems": false,
    "uploadGeneratedMedia": true,
    "accessType": "assume-role",
    "iamRoleArn": "arn:aws:iam::493738489928:role/mimir-stg-access",
    "externalId": "dmVyc2FudHN0YWdpbmcjMjMyNjFmNzgtMmQyMS00NTU2LTgwNmUtZmRhZTFlNmQxZDll",
    "storageProvider": "s3_native"
  },
  {
    "id": "mimir-stg-generated-media-live-1/",
    "bucketName": "mimir-stg-generated-media-live-1",
    "pathPrefix": "",
    "backup": false,
    "deleteEnabled": false,
    "autoCreateItems": false,
    "uploadGeneratedMedia": false,
    "mimirFolderId": null,
    "storageProvider": "s3_native",
    "accessType": "iam-user",
    "accessKey": "AKIAXF5I3PBECYEVJGF5"
  }
]

GET /prime/api/v1/storages

Get storage locations

✅ Live — responds with data

POST /prime/api/v1/storages

Create storage location

✅ Live — responds with data

Sample Response:

{
  "error": {
    "statusCode": 400,
    "message": "Request body is not a valid storage creation payload"
  }
}

Response Schema:

Field Type Required
error object Yes

Endpoints Requiring Valid Input

These endpoints are confirmed live but need proper request bodies.

GET /api/v1/storageManagers

Get Status of all the Storage Managers

🔒 Live — needs different auth scope

Sample Response:

{
  "error": {
    "statusCode": 401,
    "message": "The client is not authenticated to get the requested resource."
  }
}

Response Schema:

Field Type Required
error object Yes

Note

[401] {'statusCode': 401, 'message': 'The client is not authenticated to get the requested resource.'}

POST /ingest/api/v1/generatedMediaLocations

Create generated media location

⚠️ Live — requires valid request body

Sample Response:

{
  "error": {
    "statusCode": 400,
    "message": "Could not verify location",
    "payload": {
      "key": "AccessDenied",
      "message": "Could not attach S3 event triggers: UnknownError"
    }
  }
}

Response Schema:

Field Type Required
error object Yes

Note

[400] {'statusCode': 400, 'message': 'Could not verify location', 'payload': {'key': 'AccessDenied', 'message': 'Could not attach S3 event triggers: UnknownError'}}

DELETE /prime/api/v1/storages

Delete storage location

⚠️ Live — requires valid request body

Sample Response:

{
  "error": {
    "statusCode": 400,
    "message": "Request body is not a valid storage deletion payload"
  }
}

Response Schema:

Field Type Required
error object Yes

Note

[400] {'statusCode': 400, 'message': 'Request body is not a valid storage deletion payload'}

PUT /prime/api/v1/storages

Update storage location

⚠️ Live — requires valid request body

Sample Response:

{
  "error": {
    "statusCode": 400,
    "message": "Request body is not a valid storage update payload"
  }
}

Response Schema:

Field Type Required
error object Yes

Note

[400] {'statusCode': 400, 'message': 'Request body is not a valid storage update payload'}

Not Found

Method Path Code
GET /api/v1/generatedMediaLocations 404
GET /api/v1/ingestStorageConfigs 404
GET /api/v1/storage 404
GET /api/v1/storage/locations 404
GET /api/v1/storage/managers 404
GET /api/v1/storage/transfers 404
GET /api/v1/storageLocations 404
GET /api/v1/storages/{storageId}/transferRequests 404
POST /api/v1/storages/{storageId}/transferRequests 404
DELETE /api/v1/storages/{storageId}/transferRequests/{transferRequestId} 404
GET /api/v1/storages/{storageId}/transferRequests/{transferRequestId} 404
POST /api/v1/storages/{storageId}/transferRequests/{transferRequestId} 404
GET /api/v1/tenantStorage 404
DELETE /ingest/api/v1/generatedMediaLocations/{id} 404
GET /ingest/api/v1/generatedMediaLocations/{id} 404
PUT /ingest/api/v1/generatedMediaLocations/{id} 404