GoliathDevelopersGet an API key
Reference/Spacesgenerated from the gateway manifest

moveSpaceItems

Move up to 200 items into a folder or a root.

POST/api/v1/callWRITEidempotent · 24 hruns as the key's owner
View as Markdown

Move up to 200 items into a folder or a root (destination.folderId omitted), all or nothing. Needs edit access on both sides; a move that would change who can see an item (out of a restricted folder, or between My files and Team) also needs MANAGER on it unless it was already open to the whole team: and an AI agent can never make that kind of move: ask the person to do it in Library. Folders move with everything in them.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "moveSpaceItems",
    "variables": {
      "input": {
        "itemIds": [
          "<itemIds>"
        ],
        "destination": {
          "spaceId": "<spaceId>"
        }
      }
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

const result = await goliath.spaces.moveSpaceItems(
  {
    input: {
      itemIds: [
        '<itemIds>'
      ],
      destination: {
        spaceId: '<spaceId>'
      }
    }
  },
  { idempotencyKey: crypto.randomUUID() },
)
const res = await fetch('https://server.goliathdata.com/api/v1/call', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
    operationId: 'moveSpaceItems',
    variables: {
      input: {
        itemIds: [
          '<itemIds>'
        ],
        destination: {
          spaceId: '<spaceId>'
        }
      }
    }
  }),
})
const { data, errors } = await res.json()

Variables

The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.

inputMoveSpaceItemsInput!required
itemIds[ID!]!required
destinationSpaceDestinationInput!required
Every field, all the way down
variables
[
  {
    "name": "input",
    "type": "MoveSpaceItemsInput!",
    "required": true,
    "description": null,
    "defaultValue": null,
    "fields": [
      {
        "name": "itemIds",
        "type": "[ID!]!",
        "required": true,
        "description": null,
        "defaultValue": null
      },
      {
        "name": "destination",
        "type": "SpaceDestinationInput!",
        "required": true,
        "description": null,
        "defaultValue": null,
        "fields": [
          {
            "name": "spaceId",
            "type": "ID!",
            "required": true,
            "description": null,
            "defaultValue": null
          },
          {
            "name": "folderId",
            "type": "ID",
            "required": false,
            "description": "Null for the space root.",
            "defaultValue": null
          }
        ]
      }
    ]
  }
]

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "spacesMutation": {
      "move": [
        {
          "id": "<ID>",
          "spaceId": "<ID>",
          "spaceName": "…",
          "parentId": "<ID>",
          "kind": "FOLDER",
          "name": "…",
          "description": "…",
          "fileType": "…",
          "sizeBytes": 0,
          "accessMode": "INHERIT",
          "systemLocked": true,
          "viewerRole": "VIEWER",
          "abilities": {
            "addChildren": true,
            "edit": true,
            "move": true,
            "trash": true,
            "share": true
          },
          "owner": {
            "id": "<ID>",
            "name": "…"
          },
          "createdBy": {
            "kind": "PERSON",
            "label": "…"
          },
          "childCount": 0,
          "shareCount": 0,
          "currentVersion": {
            "id": "<ID>",
            "versionNumber": 0
          },
          "path": [
            {
              "id": "<ID>",
              "name": "…"
            }
          ],
          "updatedAt": "2026-01-01T00:00:00.000Z",
          "trashedAt": "2026-01-01T00:00:00.000Z"
        }
      ]
    }
  }
}

Errors

Idempotency

Send an Idempotency-Key of 1 to 255 characters. A finished request retried with the same key replays its stored response, marked Idempotency-Replayed: true; one still in flight returns 409 idempotency_conflict. Keys expire after 24 hours. Write without fear →