Skip to main content
Create a new blob within an organization.

POST /orgs/:id/blobs

Path Parameters

Request Body

All three are required and nothing else is accepted. There is no name field: the blob is named after its alias, which is fixed at creation — Update Blob has no alias parameter, so a blob cannot be renamed once created. type is a single dotted string, not a composite of independent fields. Five are recognized, and an organization can create one only while that type’s enabled entitlement is true for it. workflow.enabled, scheduler.enabled and onnx.enabled are true by default; orientdb.enabled and nlp.enabled are false — see Limits: Any other string, and any of these whose enabled entitlement is false for the organization, is refused with invalid_blob_type. For a recognized type the body also carries limit, naming the entitlement: {"id": "orientdb.enabled", "value": false}.

Response

The blob record exists the moment this call answers, but the rest of the creation is asynchronous: its status is creating_blob until the platform has provisioned it and its first revision, and only a ready blob accepts writes. Poll Get Blob for status and default_revision_id.

Errors

Example