Skip to main content

JSONSilo Manage API

The JSONSilo Manage API allows you to programmatically manage your JSON silos, including creating, updating, deleting silos, and reading the data and metadata stored in them.
To let an AI tool manage your silos instead of your own code, see the MCP Server.

Base URL

The base URL for the JSONSilo Manage API is structured as follows:
Replace [region-code] with the appropriate region code for your silo, and [file-uuid] with the unique identifier assigned to your JSON file.

Endpoints

The JSONSilo Manage API provides the following endpoints:
Send the Create Silo request to /api/v1/manage with no trailing slash.

Authentication

To use the JSONSilo Manage API, you need an API key for authentication. Include your API key in the X-MAN-API or x-man-api HTTP header for all API requests:
  • Replace MANAGE_API_KEY with your actual API key.
  • To generate a new API key, follow the instructions here.

Example Request

Here is an example of how to make a request using curl:
Terminal

Response Codes

Most error responses have a short plain-text message as the body, for example Invalid API Key. These have a JSON body instead:
  • 400 when the request body has the wrong shape, for example is_public is not a boolean.
  • 402 when your free trial has ended.
  • 422 when the data doesn’t match a locked schema.

Schema Lock

If a silo has a locked schema, an Update Silo request whose file_data doesn’t match it returns 422, and the stored data stays as it was:
The Manage API can’t read, change, or remove a silo’s schema. Use Get Silo Meta to check whether a silo has a schema (has_schema) and whether it is locked (schema_locked).

Rate Limits

Manage API requests are rate limited for each account, based on your plan. Responses include ManageSilo-Req-Limit, ManageSilo-Req-Remaining, and ManageSilo-Req-Reset headers. See Rate Limits.

Activity Logs

Every create, update, and delete made through the Manage API is recorded in the console’s Logs with an (API) label.