Project hot vs. cold triple storage
GET
/api/v1/projects/{projectId}/storage
const url = 'https://api.yggy.tech/api/v1/projects/example/storage';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.yggy.tech/api/v1/projects/example/storage \ --header 'Authorization: Bearer <token>'Point-in-time estimates of this project’s triple storage: hot triples in the live graph, cold triples in archive storage, and the size of the stored files.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ” projectId
required
string
Responses
Section titled “ Responses ”Project tier storage
Media type application/json
object
projectExternalId
required
string
mode
required
Effective storage policy: hot-first or cold-first
string
hotTriples
required
Estimated triples in the live graph
number
coldTriples
required
Triples in cold object storage (manifest count)
number
hydratingTriples
required
Triples currently promoting back to hot
number
blobObjects
required
Distinct cold archive blobs backing this project
number
blobBytes
required
Summed blob bytes (partial when bytesTruncated)
number
bytesTruncated
required
True when blobBytes hit the stat cap and is partial
boolean
Example generated
{ "projectExternalId": "example", "mode": "example", "hotTriples": 1, "coldTriples": 1, "hydratingTriples": 1, "blobObjects": 1, "blobBytes": 1, "bytesTruncated": true}Project not found
Media type application/json
object
success
required
boolean
error
required
object
message
required
string
code
required
string
details
Example
{ "success": false, "error": { "code": "INTERNAL_ERROR" }}