Skip to content

Create inline upload

Uploads a file of at most 2 MiB with its bytes in the call, for a client that cannot send them to an upload URL.

Needs the file:write scope.

Call

  • Tool: create_inline_upload
  • Scope: file:write
  • Writes, adding without changing what is there.
  • Acts on a store.

Arguments

Name Type Required Description
store string No The store to act on.
name string Yes
title string or null No
enforcement "public" or "signed" No How the file is served: public to anyone with its link, signed (the default) only through links that expire.
mime string Yes
ext string or null No The file’s own extension; the mime’s usual one when absent or null.
data string Yes The file’s bytes, base64 in JSON, at most 2 MiB.
{
  "type": "object",
  "properties": {
    "store": {
      "type": "string",
      "description": "The store to act on."
    },
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "pattern": "^[a-z0-9][a-z0-9-]*$"
    },
    "title": {
      "anyOf": [
        {
          "type": "string",
          "minLength": 1,
          "maxLength": 200
        },
        {
          "type": "null"
        }
      ]
    },
    "enforcement": {
      "description": "How the file is served: `public` to anyone with its link, `signed` (the default) only through links that expire.",
      "type": "string",
      "enum": [
        "public",
        "signed"
      ]
    },
    "mime": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "pattern": "^[a-zA-Z0-9][a-zA-Z0-9!#$&^_.+-]*\\/[a-zA-Z0-9][a-zA-Z0-9!#$&^_.+-]*$"
    },
    "ext": {
      "description": "The file's own extension; the mime's usual one when absent or null.",
      "anyOf": [
        {
          "type": "string",
          "minLength": 1,
          "maxLength": 16,
          "pattern": "^[a-zA-Z0-9]+$"
        },
        {
          "type": "null"
        }
      ]
    },
    "data": {
      "description": "The file's bytes, base64 in JSON, at most 2 MiB.",
      "anyOf": [
        {
          "type": "string",
          "contentEncoding": "base64"
        },
        {
          "type": "string",
          "contentEncoding": "base64"
        }
      ]
    }
  },
  "required": [
    "name",
    "mime",
    "data"
  ],
  "additionalProperties": false
}

Answer

Name Type Required Description
transforms array of object Yes
deliveries object Yes
uses object Yes
children object Yes
id string Yes
locator string or null Yes
origin string Yes
custodian string Yes
enforcement string Yes
mime string or null Yes
bytes number or null Yes The file’s size in bytes; null when it is charged nothing.
quota_bytes number Yes The file’s size in bytes; zero when it is charged nothing.
name string Yes
title string or null Yes
ext string or null Yes
status string Yes
optimized boolean Yes
parent_id string or null Yes
redacted boolean Yes
security string or null Yes
description string or null Yes
processed_at string or null Yes
metadata object Yes
created_at string or null Yes

The answer’s full shape is on its API reference page.

Errors

A refused call is a tool error. Its structuredContent holds a code and its context, except for client-fault. This tool may answer:

  • invalid: an argument is malformed; context.path names it.
  • invalid at ["store"]: store is missing while the connection reaches more than one store, or names a store it doesn’t reach.
  • conflict: the call clashes with the current state; context names the field and, where it helps, its current value, and for a from, live, expect or version that no longer matches, the argument (path) and what it takes (reason).
  • not_permitted: this connection may not make this call. When context.reason is limit, too many calls: retry_after says when to try again.
  • internal or unavailable: the call failed inside Sherpo, and the write may have landed. This write takes no idempotency key, so read the state back before trying again.
  • client-fault: the server failed around the call. core_answer ok means the write landed, so don’t send it again. When reached_core is false, nothing happened and the call may be made again. Otherwise, this write takes no idempotency key, so read the state back before trying again.
  • HTTP 403 with insufficient_scope: the connection lacks the scope this tool needs.
  • HTTP 401 with invalid_token: the access token expired or the connection ended. Refresh the token, and connect again if the refresh fails or the new token is refused too.

Any other code may come back too, such as a conflict when the state changed under the call. When the answer was already streaming, a 401 or 403 comes back as a tool error with only its text. See Errors for every code and its context.

Type to search…

↑↓ navigate↵ selectEsc close